Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

Register SAP Agent (Raw SDK Deprecated)

sap_register_agent

Registers an SAP agent with display name, pricing tiers, protocols, and capabilities via the raw SDK. Deprecated; production uses the canonical payment-confirmed path.

Instructions

Deprecated raw SDK wrapper. Production registration must use sap_payments_register_agent so the local signer path confirms the account, verifies the 0.1 SOL protocol treasury fee invariant, and returns protocolComplete. Hosted accountless SAP MCP rejects this direct write before x402 payment. SAP MCP context: Do not use this raw SDK wrapper for production registration. The canonical registration path is sap_payments_register_agent, because it confirms the account, audits the protocol treasury fee, and fails closed when protocolComplete is false. Hosted accountless SAP MCP rejects direct registration before x402 payment because OOBE never custodies user wallet keys. Use sap_agent_identity_plan first, then sap_payments_register_agent with confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRequired public display name for the SAP agent. Keep it stable enough for explorers and humans.
agentIdNoOptional stable lowercase agent id, for example solking. This is separate from the on-chain agent PDA.
pricingNoOptional pricing tiers advertised by the agent. Use tokenType usdc + settlementMode x402 for pay.sh/x402 agent commerce.
agentUriNoOptional public HTTPS/IPFS/Arweave/Kommodo URI for the agent profile metadata or profile page. Never use local desktop file paths.
protocolsNoRequired protocol tags the agent supports, for example sap, mcp, jupiter, pyth, metaplex, sns, x402, payments.
descriptionNoRequired public description of what the agent does, which protocols it can use, and its safety/trust boundaries.
metadataUriNoAlias for agentUri. Prefer a public JSON metadata document containing name, description, image, external_url, attributes, sap, metaplex, sns, and x402 fields.
capabilitiesNoRequired capability list. Prefer object form for production; strings are accepted as shorthand.
x402EndpointNoOptional public x402 discovery/payment endpoint, usually https://host/.well-known/x402 for external agent services.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesMCP content blocks returned to the caller.
isErrorNoTrue when the tool result represents an application-level error.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses deprecation, raw SDK nature, and that Hosted accountless SAP MCP rejects direct writes before x402 payment, adding context beyond annotations. Annotations provide readOnlyHint=false and openWorldHint=true, consistent with the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is repetitive, restating the deprecation and alternative multiple times. It could be trimmed to be more front-loaded; the first sentence is good but subsequent sentences add redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (deprecated, with alternative, 9 parameters), the description is fairly complete. It provides reasoning for deprecation and context about Hosted SAP MCP. Output schema exists, so return values are not needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description does not need to add parameter details. Baseline 3 is appropriate; the description does not significantly enhance parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a deprecated raw SDK wrapper for SAP agent registration, and distinguishes it from the canonical sap_payments_register_agent. The verb 'register' and resource 'agent' are explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises against using this tool for production and directs to sap_payments_register_agent. It also mentions to use sap_agent_identity_plan first, providing clear when-not and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OOBE-PROTOCOL/sap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server