{"uid":"cap_SuzuxOUwSZ5sTBnseG60R","slug":"mcp-tool-definition-normalizer-1dc7c430","name":"MCP Tool Definition Normalizer","description":"Takes a list of MCP tool definitions, as returned by tools/list on any number of servers, and rewrites them into one common form. Servers disagree on where the schema lives — inputSchema, input_schema, parameters, schema or arguments are all in use — and a consumer reading only one of them loses the others silently; every spelling is accepted and the one found is reported.","url":"https://agent.halowerk.com/v1/mcp-normalize","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"tools":{"type":"array","items":{"type":"object","required":["name"],"properties":{"name":{"type":"string","minLength":1,"description":"Tool name."},"server":{"type":"string","description":"Which server the tool came from. Used for collision reporting."}}},"maxItems":200,"minItems":1,"description":"The MCP tool definitions to normalise."},"naming":{"enum":["snake_case","preserve"],"type":"string","default":"snake_case","description":"How to normalise tool names."},"include_examples":{"type":"boolean","default":true,"description":"Build a synthetic example call per tool."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_AGgnMyXN7ANEGe7m36htr","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Accepts a list of MCP tool definitions from one or more servers and rewrites them into a single, consistent schema form, resolving variations in field names like inputSchema, input_schema, parameters, schema, and arguments.","exampleAgentPrompt":"I just fetched tool definitions from three different MCP servers and they all use different field names — some use inputSchema, others use parameters or arguments. Can you normalize all of them into one consistent shape so I can process them uniformly?","exampleUseCases":[{"title":"Multi-server MCP tool aggregation","prompt":"I'm pulling tool definitions from five MCP servers and each one uses a different field name for the schema — inputSchema, parameters, schema, you name it. Can you normalize all of them into one common format so my agent can read them consistently?"},{"title":"Debugging silent schema field loss","prompt":"My agent is consuming MCP tool definitions but silently dropping tools from some servers because the schema field name doesn't match what it expects. Can you run these tool definitions through the normalizer so I can see which field name each server is using and get them all into one unified shape?"},{"title":"Building a unified MCP tool registry","prompt":"I'm building a tool registry that aggregates MCP tools from many sources. The raw tools/list responses I've collected use at least four different field name conventions. Please normalize all these tool definitions into a single consistent form so I can index them reliably."}],"resultDescription":"A list of rewritten MCP tool definitions in a single canonical schema form, with each tool's schema field unified to one consistent name regardless of the original spelling (inputSchema, input_schema, parameters, schema, or arguments). The response also reports which field name variant was found for each tool.","failureModes":["Input list is empty — returns an error or empty result","Tool definition lacks any recognized schema field — tool may be returned without a schema or flagged","Malformed JSON in tool definitions — parse error returned","Unrecognized schema field variant not in the known set — silently passed through or flagged"],"whenToPreferThis":"Choose this endpoint when your agent consumes MCP tool definitions from multiple servers that use inconsistent field naming conventions and you need a single canonical representation before further processing, routing, or indexing. It is the right choice when silent field loss from schema name mismatches is a concern and when you need to know exactly which variant each server used.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-13T18:45:54.222Z","isFirstParty":false}