Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

by OOBE-PROTOCOL
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Update SAP Agent

sap_update_agent

Update an SAP agent's configuration including name, description, capabilities, pricing, protocols, and metadata after registration.

Instructions

Local-signer-only: update the connected wallet SAP agent using SDK AgentModule.update. Hosted accountless SAP MCP rejects this direct write before x402 payment; hosted users should call sap_payments_update_agent from the local sap_payments bridge. SAP MCP context: Use this after sap_register_agent to refresh name, description, capabilities, pricing, supported protocols, x402 endpoint, or metadataUri. For NFT-backed identity changes, update the Metaplex asset first when needed, then point the SAP agent metadataUri at the current metadata document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional replacement display name. Omit to keep the current name.
agentIdNoOptional replacement stable agent id. Omit to keep current agentId.
pricingNoOptional full replacement pricing tier list. Omit to keep current pricing.
agentUriNoOptional replacement public URI for agent metadata/profile. Use this to update pictures after uploading metadata to IPFS, Arweave, Kommodo, or HTTPS.
protocolsNoOptional full replacement protocol list. Omit to keep current protocols.
descriptionNoOptional replacement description. Omit to keep the current description.
metadataUriNoAlias for agentUri. Use a public metadata JSON URI; never use a desktop file path.
capabilitiesNoOptional full replacement capability list. Omit to keep current capabilities; do not send only the new item unless replacing the whole list is intended.
x402EndpointNoOptional replacement x402 discovery/payment endpoint. Omit to keep current endpoint.

Output Schema

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

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Discloses local-signer requirement and SDK method. Annotations already indicate readOnlyHint=false and destructiveHint=false, but description adds context about rejection for hosted users. Does not contradict annotations.

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

Conciseness5/5

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

Five sentences, front-loaded with critical context (local-signer-only, alternative), no redundancy, every sentence provides essential guidance.

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

Completeness5/5

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

Given 9 optional parameters and output schema, description covers main use cases, prerequisites, alternatives, and parameter tips. Output schema reduces need to explain return values.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by listing updatable fields, providing usage tips (e.g., NFT identity workflow, warning about replacing entire lists).

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?

Clearly states 'update the connected wallet SAP agent' with specific verb+resource. Distinguishes from sibling sap_payments_update_agent by specifying 'Local-signer-only' provides alternative for hosted users.

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?

Explicitly states when to use (after sap_register_agent), when not to use (hosted accountless MCP rejects direct write), and directs to alternative sap_payments_update_agent. Also provides prerequisite for NFT-backed identity changes.

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