Skip to main content
Glama
Sign In

Docstar

by io.github.swayammaheshwari
OverviewDiscussionsAdmin

call_any_api_of_docstar

Destructive

Send a POST, PUT, PATCH or DELETE request to any DocStar API endpoint for the signed-in user and return { status, ok, headers, data }. Use it for changes no dedicated tool covers, once you know the exact endpoint: from the quickstart-docstar skill's recipes, or looked up with get_docstar_api_docs. For GET requests use call_any_read_api_of_docstar. Never guess a URL. Pass the full url with path variables filled in, the method, the headers the endpoint's docs list, query params in query (not in the url) and the JSON body in body. Send the endpoint's auth header with an empty value "": the user's token is filled in automatically. Never put a token there yourself. Show the user what you're about to send and get a yes before any call that creates, changes, publishes or deletes something.

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": {
      "url": "<url>",
      "headers": "<headers>",
      "method": "<method>"
    },
    "name": "call_any_api_of_docstar"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here.
bodyNoJSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body.
queryNoQuery params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true}
methodYesHTTP method from the endpoint's docs
headersYesRequest headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {"proxy_auth_token": "", "Content-Type": "application/json"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructive/openWorld/non-idempotent, but the description adds real substance: the return shape {status, ok, headers, data}, the automatic token-injection mechanism (send auth header empty, never supply a token yourself), and a mandatory confirmation step before mutating calls. It stops short of describing error/failure semantics beyond the `ok` field, which keeps it off a 5.

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 alternatives, then a call recipe and a safety rule — a logical ordering with no filler sentences. It is on the long side and several clauses duplicate the schema, but each sentence does convey operational information.

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 5-parameter, nested-object, destructive write tool with no output schema, the description supplies the return shape, the auth convention, endpoint-discovery path, and the human-confirmation requirement. An agent has everything needed to call it correctly and safely.

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

Parameters3/5

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

Schema coverage is 100% and the schema descriptions already carry the key guidance (full URL with path variables, query in `query` not the URL, auth header empty value). The description restates rather than extends that, so the baseline 3 applies.

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?

States a specific verb set (POST/PUT/PATCH/DELETE) and resource (any DocStar API endpoint) for the signed-in user, and explicitly routes GET requests to the sibling tool call_any_read_api_of_docstar. An agent can distinguish it from the read variant without opening either schema.

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?

Gives explicit when-to-use (changes no dedicated tool covers, once the exact endpoint is known), where to get the endpoint (quickstart-docstar recipes or get_docstar_api_docs), the exclusion (GET goes to the read sibling), and a hard constraint (never guess a URL). Nothing is left to inference.

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

All Docstar toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources