Skip to main content
Glama

x402 Structured Data & URL Scraper

parse_web_schema

Read-only

Fast key-value entity extraction from raw web or document text when you only need a flat list of named fields rather than a full nested JSON Schema. Ideal for pulling contacts, dates, tickers, or metadata out of messy text (max 6,000 bytes).

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": {
      "content": "<content>",
      "fields": "<fields>"
    },
    "name": "parse_web_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesExact entity or field names to extract as keys.
contentYesRaw web or document text to scan (max 6,000 bytes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / fields / examples
      Removed value: -[
      -  [
      -    "company_name",
      -    "ceo",
      -    "headquarters",
      -    "founded_year"
      -  ]
      -]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read over supplied text. The description confirms the input is raw text rather than a URL and repeats the 6,000-byte cap, but adds little behavioral context beyond the annotations and schema — no failure behavior for oversized input, no indication of what happens when a requested field is absent.

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 tight sentences with the capability and the selection condition front-loaded. Minor redundancy: the 6,000-byte cap appears in the description and again in both schema fields.

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?

For a two-parameter, fully documented, non-destructive extraction tool with no output schema, the description conveys both input expectations and the shape of the result ('flat list of named fields'). Nothing critical is missing, though a note on handling of missing fields would round it out.

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 description coverage is 100%, so both parameters are already documented and the baseline is 3. The description reinforces the semantics ('named fields' as keys, 'messy text' as the scan target) but adds no format, casing, or matching guidance beyond the 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 concrete verb and resource: key-value entity extraction from raw web or document text, and adds a scope qualifier ('flat list of named fields rather than a full nested JSON Schema') that separates it from a schema-producing sibling like extract_structured_data. It stops short of naming the sibling, so the distinction is inferential rather than explicit.

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

Usage Guidelines4/5

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

Gives a clear selection condition (use when you need a flat key-value list, not a nested schema) and concrete example targets (contacts, dates, tickers, metadata). It does not name the alternative tool or state exclusions, but the when-to-use context is unambiguous.

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