Skip to main content
Glama

textokit_sample

Free sample of one route (same schema as the paid output) plus an inputExample. Use it before paying.

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": {
      "route": "<route>"
    },
    "name": "textokit_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "translate-es",
      -  "base-usdc-receipts",
      -  "bcra-indicadores",
      -  "cartas-ar",
      -  "comparar-textos",
      -  "crypto-prices",
      -  "cuit-ar",
      -  "dev-utils",
      -  "direcciones-ar",
      -  "dolar-ar",
      -  "fx-rates",
      -  "lead-followup-kit",
      -  "normativa-ar",
      -  "polymarket-markets",
      -  "source-bounded-summary",
      -  "url-text",
      -  "web-read",
      -  "x402-adoption",
      -  "x402-ping"
      -]New value: +[
      +  "translate-es",
      +  "base-usdc-receipts",
      +  "bcra-indicadores",
      +  "cartas-ar",
      +  "comparar-textos",
      +  "crypto-prices",
      +  "cuit-ar",
      +  "dev-utils",
      +  "direcciones-ar",
      +  "dolar-ar",
      +  "fx-rates",
      +  "lead-followup-kit",
      +  "normativa-ar",
      +  "polymarket-markets",
      +  "source-bounded-summary",
      +  "url-text",
      +  "web-read",
      +  "webhook-log-audit",
      +  "x402-adoption",
      +  "x402-ping"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "translate-es",
      -  "base-usdc-receipts",
      -  "bcra-indicadores",
      -  "cartas-ar",
      -  "comparar-textos",
      -  "crypto-prices",
      -  "cuit-ar",
      -  "dev-utils",
      -  "direcciones-ar",
      -  "dolar-ar",
      -  "fx-rates",
      -  "normativa-ar",
      -  "polymarket-markets",
      -  "source-bounded-summary",
      -  "url-text",
      -  "web-read",
      -  "x402-adoption",
      -  "x402-ping"
      -]New value: +[
      +  "translate-es",
      +  "base-usdc-receipts",
      +  "bcra-indicadores",
      +  "cartas-ar",
      +  "comparar-textos",
      +  "crypto-prices",
      +  "cuit-ar",
      +  "dev-utils",
      +  "direcciones-ar",
      +  "dolar-ar",
      +  "fx-rates",
      +  "lead-followup-kit",
      +  "normativa-ar",
      +  "polymarket-markets",
      +  "source-bounded-summary",
      +  "url-text",
      +  "web-read",
      +  "x402-adoption",
      +  "x402-ping"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "translate-es",
      -  "bcra-indicadores",
      -  "cartas-ar",
      -  "comparar-textos",
      -  "crypto-prices",
      -  "cuit-ar",
      -  "dev-utils",
      -  "direcciones-ar",
      -  "dolar-ar",
      -  "fx-rates",
      -  "normativa-ar",
      -  "polymarket-markets",
      -  "source-bounded-summary",
      -  "url-text",
      -  "web-read",
      -  "x402-adoption",
      -  "x402-ping"
      -]New value: +[
      +  "translate-es",
      +  "base-usdc-receipts",
      +  "bcra-indicadores",
      +  "cartas-ar",
      +  "comparar-textos",
      +  "crypto-prices",
      +  "cuit-ar",
      +  "dev-utils",
      +  "direcciones-ar",
      +  "dolar-ar",
      +  "fx-rates",
      +  "normativa-ar",
      +  "polymarket-markets",
      +  "source-bounded-summary",
      +  "url-text",
      +  "web-read",
      +  "x402-adoption",
      +  "x402-ping"
      +]
  4. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral facts: the call is free and the response mirrors the paid schema. It omits whether sample output is truncated or limited in size, rate limits, and any auth/payment gating — all material for a sampling endpoint.

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?

Two short sentences with the core facts front-loaded and no filler. The trailing "plus an inputExample" is jargon that is not explained, which slightly undercuts 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 20-value dispatching/sampling tool with no output schema and no annotations, the description leaves too much unanswered: how the sample differs from the paid response, whether results are truncated, and how route values map to the sibling tools. An agent can call it, but cannot predict what it gets back.

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 coverage is 0% and there is one required enum parameter whose semantics are unexplained. The phrase "one route" does not tell the agent that values correspond to the 20 sibling tool names, nor what happens if an unsupported value is passed (additionalProperties is false).

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?

"Free sample of one route (same schema as the paid output)" states a specific action and resource: a trial invocation parameterized by route. It distinguishes itself from the per-route paid siblings by being the sampling entry point, though it never states that the enum values correspond to those sibling tools.

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

Usage Guidelines3/5

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

"Use it before paying" gives one clear usage context (pre-purchase evaluation), which is genuinely useful routing guidance. However, it never says when NOT to use it or names the alternative to call once the agent has decided to pay.

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.