Person
NAGARJUN DAS
GitHub@Nagarjundas1994-AiAgentslast push
Capabilities
Provides
Agent toolingCAPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.Input validationCAPInput validationRejecting bad input before it reaches the database. While this can be done manually inside a handler, there are solutions in place to derive type, range, enum and mandatory checks from the model definitions.Tool governanceCAPTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.
Entries
Group by
EntrySignals
Maintains
cds-agentscds-agentsTurns a CAP service into a tool layer for agent frameworks — a CAPToolkit bound to a named service, with a tool strategy controlling how much of it becomes callable.independent, cap
Toolkit turning a CAP service into tools for agent frameworks
cds-validatecds-validateA package that runs Zod schemas as CAP validation middleware, so one schema replaces the hand-written checks at the top of a handler and failures come back as OData 422 errors per field.independent, cap
Zod schemas as CAP validation middleware
Details
History
- cds-agentsThe entry stated the capability with no source, and its paragraph said the framework is the host without the fact that makes this entry different from every other option here: the README states it is a client library pointed at something already running, where @cap-js/mcp is a plugin whose application you must own. Read on 2026-10-15, which also gives the three entry points as the README scopes them, the toolStrategy values, the four-hundred-tool argument behind them, and the install line, which replaced an unsourced claim about four peer dependencies. The tool-governance edge is untouched: its claims belong to that capability's own pass.
- cds-agentscapability:agent-tooling declared four comparison properties on 2026-10-15. Both brings values rest on their own sentence — CAPToolkit is the raw-tool layer and the production default, CAPAgent a ready-made ReAct agent for demos and small apps — and the protocol is the one its own executor names as a client, not a protocol it serves. The state and approval properties are left out: the README says nothing about either.
- First entry seenDiscovered via npm registry · keywords:sap-cap, npm registry · keywords:cds.
For your agent
- Ref
actor:nagarjundas1994-aiagents- JSON
- /actors/nagarjundas1994-aiagents.json
- MCP
- Connecting an agent