CallMeter

extract.webpage

Read-onlyIdempotent

Fetch a public http(s) URL and return structured page facts as JSON (SSRF and robots checks refuse unsafe URLs). Call when the agent has a page URL to understand — not when text/HTML is already in hand (use extract.structured_data) and not for a visual capture (use capture.screenshot). Inputs: required url; optional instruction, schema, require_llm. Outputs structured JSON about the page. Paid (~5 credits / $0.05) via prepaid key or x402.

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>"
    },
    "name": "extract.webpage"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Public http(s) URL to fetch and structure. Example: https://example.com/about
`schema`	No	Optional JSON Schema the page extract should satisfy
`instruction`	No	Optional focus hint for extraction. Example: 'Extract company name and contact emails'
`require_llm`	No	If true and enrichment LLM unavailable → processing failure. Example: false

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is the SSRF and robots-check refusal behavior, plus the paid cost (~5 credits / $0.05) and payment paths (prepaid key or x402). That is real context beyond structured fields, though it omits failure modes or limits on what 'page facts' includes (left to the output schema).

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 routing, then inputs/outputs, then cost. Efficient, though the trailing 'Inputs:/Outputs:' enumeration partly repeats what the schema and output schema already declare.

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?

Given the presence of an output schema and rich annotations, the description covers all the gaps that matter for invocation: routing, security refusals, cost, and payment method. Nothing an agent needs before calling is missing.

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 each parameter already carries its own description and examples. The description only re-lists parameters by name ('required url; optional instruction, schema, require_llm') without adding semantics beyond the schema, so 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 and resource ('Fetch a public http(s) URL and return structured page facts as JSON') and immediately names the two siblings it is not (extract.structured_data, capture.screenshot). An agent can route correctly without opening any 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 an explicit when-to-call condition ('agent has a page URL to understand') and two explicit when-not conditions with the alternative tool named for each. Nothing about routing 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 CallMeter tools Inspect

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

Need Help?