Skip to main content
Glama

api

Destructive

Call platform /v1 endpoints that do not have a dedicated MCP tool yet. Dedicated tools cover common operations; this tool covers the remaining and newly added endpoints. catalog lists existing tools and docs({ topic }) documents endpoint shape.

Each request is explicit and inspectable: calls is a flat array of independent { method, path, body? } items. A single invocation runs up to 10 calls, each still endpoint-auth and quota gated. Data from one call is not inserted into another; data-dependent chains run across separate tool calls. path must be a platform /v1/... path, not a full URL.

Write calls require confirm:true by default. GET and HEAD run without confirm; POST /v1/ai/complete and POST /v1/ai/embed are the only read-shaped write routes currently allowlisted. Without confirmation the tool returns the exact calls it would run and asks you to re-call with confirm:true. Calls run with the caller's own auth and the same permission checks as dedicated tools.

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": {
      "calls": "<calls>"
    },
    "name": "api"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYesFlat list of independent platform API calls. Max 10. No templating or substitution between calls.
confirmNoRequired as true for any POST, PUT, PATCH, or DELETE unless the normalized route is explicitly allowlisted as read-shaped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description adds substantial context beyond that: a 10-call cap, per-call endpoint auth and quota gating, no data substitution between calls, path normalization/rejection rules, caller-own-auth permission parity, and the confirm gate with its exact dry-run response. The GET/HEAD exemption and the allowlisted read-shaped write routes (POST /v1/ai/complete, /v1/ai/embed) are precisely the operational detail an agent cannot infer.

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?

Front-loaded with purpose, then progressively discloses call-array semantics, path rules, and the confirm flow; every paragraph carries distinct information. Minor filler exists ("Each request is explicit and inspectable") and the density is high, but nothing is redundant.

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?

For a generic escape-hatch endpoint caller with no output schema, the definition covers safety gating, batching limits, auth model, path validation, and even the shape of the unconfirmed response. There is no obvious gap an agent would need filled before calling it correctly.

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% and already documents path rejection rules and the confirm requirement, so the baseline is 3. The description still adds meaning the schema does not: that omitting confirm returns the exact calls that would run and asks for a re-call, and that `calls` items are independent with no templating or substitution.

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 first sentence gives a specific verb and resource (call platform /v1 endpoints) and immediately scopes it to endpoints without a dedicated MCP tool, which distinguishes it from every sibling in the catalog. It also points to `catalog` and `docs({ topic })` as the discovery path for what is covered.

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 this tool (remaining and newly added endpoints) versus the alternative (dedicated tools for common operations), and routes the agent to `catalog` for tool listing and `docs` for endpoint shape. The constraint that data-dependent chains must run across separate tool calls is a clear usage rule.

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.

Resources