Skip to main content
Glama
Sign In

agentdiet

by io.github.robertoyanguas-ops
OverviewDiscussionsAdmin

recon_webpage_skeleton

Read-onlyIdempotent

Extract an ultra-compact structural outline (under ~200 tokens) of a web page listing its H1-H4 headings and exact token count per section without returning body prose. WHEN TO USE: Call this tool first on long or unfamiliar pages to inspect structure and token cost before calling distill_webpage (with mode='budget' and a focused query). WHEN NOT TO USE: Do not use when you already need full Markdown prose (use distill_webpage) or structured tables and JSON-LD (use extract_structured_data). PARAMETER INTERACTIONS: Provide either url or html (when html is supplied, url is not fetched and only labels the cache key). Omit agent_id and tx_hash during your 5 free calls. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.0002 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: recon_webpage_skeleton(url='https://docs.stripe.com/api')

Input Schema

NameRequiredDescriptionDefault
urlYesTarget public HTTP(S) webpage URL to fetch (or builtin://stripe-docs for a built-in benchmark page). Private/loopback IPs are blocked.
htmlNoOptional raw HTML string (up to ~1.9MB) to process directly without network fetching. When provided, url is not fetched and only labels the cache entry.
tx_hashNoOptional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
agent_idNoOptional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.

Output Schema

NameRequiredDescriptionDefault
dataNoStructured tool output payload.
statusYesExecution status ('ok' or 'payment_required').
roi_proofNoToken compression and cost-savings verification metrics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://docs.stripe.com/api"
+  }
+]
  2. Changed12 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."
    • addedInput schema / properties / agent_id / maxLength
      Added value: +256
    • addedInput schema / properties / agent_id / minLength
      Added value: +1
    • changedInput schema / properties / html / description
      Previous value: -"Raw HTML (up to ~1.9MB) to process instead of fetching url. When set, url only labels the cache entry."New value: +"Optional raw HTML string (up to ~1.9MB) to process directly without network fetching. When provided, url is not fetched and only labels the cache entry."
    • changedInput schema / properties / tx_hash / description
      Previous value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."
    • addedInput schema / properties / tx_hash / maxLength
      Added value: +256
    • addedInput schema / properties / tx_hash / minLength
      Added value: +10
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL to fetch, or builtin://stripe-docs for a demo page. Private and metadata IPs are blocked."New value: +"Target public HTTP(S) webpage URL to fetch (or builtin://stripe-docs for a built-in benchmark page). Private/loopback IPs are blocked."
    • addedOutput schema / properties / data / description
      Added value: +"Structured tool output payload."
    • addedOutput schema / properties / roi_proof / description
      Added value: +"Token compression and cost-savings verification metrics."
    • addedOutput schema / properties / status / description
      Added value: +"Execution status ('ok' or 'payment_required')."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "type": "object"
+    },
+    "roi_proof": {
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  4. Changed6 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."
    • changedInput schema / properties / html / description
      Previous value: -"Optional raw HTML string"New value: +"Raw HTML (up to ~1.9MB) to process instead of fetching url. When set, url only labels the cache entry."
    • changedInput schema / properties / html / maxLength
      Previous value: -99999New value: +1900000
    • changedInput schema / properties / tx_hash / description
      Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."
    • changedInput schema / properties / url / description
      Previous value: -"Target webpage URL"New value: +"Public http(s) URL to fetch, or builtin://stripe-docs for a demo page. Private and metadata IPs are blocked."
    • changedInput schema / properties / url / maxLength
      Previous value: -99999New value: +2048
  5. Changed3 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "Optional Agent ID or Session Pass (agd_pass_...)",
+  "type": "string"
+}
    • addedInput schema / properties / tx_hash
      Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}
  6. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / html / maxLength
      Added value: +99999
    • addedInput schema / properties / html / minLength
      Added value: +1
    • addedInput schema / properties / url / maxLength
      Added value: +99999
    • addedInput schema / properties / url / minLength
      Added value: +1
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: 1-hour caching with <5ms cache hits, $0.0002 per call, 5 free calls per agent_id, failed calls never charged, and the payment-required quote being a non-fatal error with retry paths (agd_pass_ key or tx_hash). This is unusually rich operational context.

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, then usage, then payment mechanics, with no wasted throat-clearing. It is dense and long, and the pricing detail ('first 5 calls per agent_id are free') partially repeats the earlier free-call instruction, costing it the top score.

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 explained; the description instead covers the auth/payment lifecycle, caching, and input alternatives. Nothing an agent needs to invoke this correctly is missing.

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, but the description adds cross-parameter interaction guidance the schema only states per-field: 'Provide either url or html (when html is supplied, url is not fetched and only labels the cache key)' and 'Omit agent_id and tx_hash during your 5 free calls'. That is genuine added value over the individual field descriptions.

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 ('Extract an ultra-compact structural outline... listing its H1-H4 headings and exact token count per section') with a clear negative scope ('without returning body prose'). It distinguishes itself cleanly from distill_webpage and extract_structured_data by naming them.

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?

Contains explicit WHEN TO USE ('first on long or unfamiliar pages to inspect structure and token cost before calling distill_webpage') and WHEN NOT TO USE sections, each naming the correct alternative and the condition that selects it. No inference is required from the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agentdiet toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources