sap_publish_tool_by_name
InactiveTool of SAP MCP Server
Publish a tool descriptor using SDK ToolsModule.publishByName. SAP MCP context: Use tool registry writes to advertise concrete capabilities that this MCP can serve, including AgentKit bridge tools such as bridging_bridgeWormhole and Metaplex tools such as metaplex-nft_mintNFT. Publish only schemas and descriptions that match the actual MCP tool surface.
Parameters schema
{
"type": "object",
"properties": {
"category": {
"type": "number",
"description": "Numeric tool category ID"
},
"toolName": {
"type": "string",
"description": "Name of the tool to publish"
},
"httpMethod": {
"type": "number",
"description": "HTTP method code (e.g. 0=GET, 1=POST)"
},
"isCompound": {
"type": "boolean",
"description": "Whether the tool is a compound tool (default: false)"
},
"protocolId": {
"type": "string",
"description": "Protocol ID the tool belongs to (e.g. \"jupiter\")"
},
"description": {
"type": "string",
"description": "Human-readable description of the tool"
},
"paramsCount": {
"type": "number",
"description": "Total number of parameters the tool accepts"
},
"requiredParams": {
"type": "number",
"description": "Number of required parameters"
},
"inputSchemaJson": {
"type": "string",
"description": "JSON string of the tool input schema"
},
"outputSchemaJson": {
"type": "string",
"description": "JSON string of the tool output schema"
}
}
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries