Skip to main content
Glama

Extract structured fields from a web page or text

extract
Read-only

Structured data from a web page (url) or your own text: give a schema of up to 20 field names with what each holds, and get a JSON object with exactly those fields, null where the text does not state one. Llama 3.3 70B. Text is capped at 12,000 characters; a model answer that is not JSON is retried once, then not charged. Price: $0.004 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlNoWeb page to read (or text)
textNoText to read (up to 12,000 characters), instead of url
schemaYesField name to what the field holds, up to 20 fields
instructionsNoOptional extra instructions, up to 500 characters

Output Schema

NameRequiredDescriptionDefault
noteNo
modelNo
fieldsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the model (Llama 3.3 70B), the 12,000-character text cap, a single retry when the model answer is not JSON, and the exact billing behavior ($0.004 per successful call, failures not charged, x402 USDC payment across multiple chains). That is unusually rich context for cost-sensitive invocation. It omits output size expectations or latency, which keeps it from 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?

One tightly packed sentence followed by two short operational sentences; purpose and output shape are front-loaded before model, limits, retry, and price. Every clause carries information, though the payment-network enumeration ('Solana and 10 more networks') is closer to marketing than to invocation guidance.

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?

An output schema exists, so return values need not be described, and annotations cover safety and openness. The description fills the remaining gaps an agent actually needs: input limits, retry-on-invalid-JSON behavior, and full cost/payment semantics. Nothing material is missing for correct invocation.

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%, so the baseline is 3; the description earns an extra point because it explains what the required `schema` parameter produces — a JSON object with exactly those fields and null where the source text lacks a value. That output contract is more useful than a restatement of the field limit, which the schema already documents.

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 verb and resource: give a schema of field names for a web page (url) or supplied text and receive a JSON object with exactly those fields. The input/output contract is unambiguous, so an agent knows precisely what it gets back. It stops short of naming how it differs from siblings like invoice_extract or classify, which keeps it below a 5.

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 rather than stated: the agent can infer 'pass url for a page, text for your own content, or both-with-schema to define fields.' The phrase 'instead of url' gives a light selection rule between the two input modes. There is no explicit when-to-use vs. when-not-to-use guidance and no routing to alternative extraction siblings.

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