Skip to main content
Glama

Expand API route parameters

bpj_expand_api_route
Read-onlyIdempotent

Substitute parameters into a relative API route, encoding each inserted path segment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "template": "<template>",
      "parameters": "<parameters>"
    },
    "name": "bpj_expand_api_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYes
parametersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, closed-world, and non-destructive. The description usefully adds that inserted path segments are encoded, but it doesn't describe failure behavior for missing parameters, extra keys, or invalid placeholders.

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

Conciseness4/5

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

The single sentence is front-loaded and free of filler, but its brevity contributes to the missing parameter guidance rather than purely enhancing clarity.

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

Completeness2/5

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

For a two-parameter tool with no schema descriptions and no output schema, the description is too thin. An agent cannot reliably know how to format the route template or the parameters object, which is essential for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining both parameters. It does not explain the placeholder syntax for 'template' nor the expected keys and value types for the 'parameters' JSON object, leaving the agent without enough detail to construct valid inputs.

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

Purpose4/5

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

The description states a specific action and resource: substitute parameters into a relative API route, with path-segment encoding. It is clear enough to distinguish this utility from unrelated siblings, though it doesn't say how substitution is signaled in the template.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is mentioned. The phrase 'relative API route' implies a URL-building context, but the agent is left to infer the intended call site.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.