Skip to main content
Glama

Tolca: business verification (KYB)

extract

extract
Read-onlyIdempotent

Extract structured data from messy text into clean JSON. Input: text, schema (JSON object describing desired fields). Costs $0.02 USDC per call (x402 v2, Base or Solana). Send the HTTP header PAYMENT-SIGNATURE with your x402 payment, or call POST https://tolca.tonbot.ca/v1/extract with an x402 client.

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": {
      "text": "<text>",
      "schema": "<schema>"
    },
    "name": "extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessy text to turn into JSON (up to 40,000 characters)
schemaYesField name -> type or description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / text / description
      Added value: +"Messy text to turn into JSON (up to 40,000 characters)"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the paid-call model ($0.02 USDC per call via x402 v2 on Base or Solana), the required PAYMENT-SIGNATURE header, and the underlying HTTP endpoint. It omits rate limits, failure/refund behavior on payment errors, and output shape beyond 'clean JSON', keeping it short of 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 the core purpose in the first sentence, followed by input, price, and payment mechanics — each sentence carries operational information. The 'Input:' clause partly duplicates the schema, which is a small redundancy.

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

Completeness4/5

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

With no output schema, the description still indicates the return is clean JSON matching the caller-supplied schema, and it fully covers the unusual payment-access path an agent must follow to invoke the tool. No nested-object or max-length caveats are repeated, but those live in the schema.

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%, so the schema already documents both parameters with length bounds and the field-map semantics. The description restates them ('text, schema (JSON object describing desired fields)') adding only a light gloss on the schema argument, which is the correct baseline for a fully documented schema.

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?

States a specific verb and resource: 'Extract structured data from messy text into clean JSON', and the input clause ('text, schema') makes clear it operates on supplied text, implicitly distinguishing it from the URL-fetching sibling extract_url. It does not name any sibling explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied by the description of the input (messy text plus a target schema), but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as extract_url or summarize for cases where the agent has a URL rather than raw text.

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.