Skip to main content
Glama

web_tools_metadata

[$x402 pago por llamada] Extrae metadata HTML (title, meta description, canonical, favicon, Open Graph) de una página.

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": "web_tools_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose the paid-per-call model ('$x402 pago por llamada'), which is real value the schema only partially mirrors. It says nothing about failure modes, whether the page must be publicly reachable, or rate/timeout behavior, and there is no output schema to cover the return contract.

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?

A single sentence with zero filler, and the pricing/billing caveat is front-loaded in brackets so the agent sees cost implications before the operation. Density is good, though the bracketed tag is slightly cryptic without knowledge of x402.

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

Completeness3/5

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

It lists the extracted fields, which partially substitutes for the missing output schema, and the schema explains the 402 flow. But for a no-annotation, no-output-schema tool, the description leaves the return shape (empty/missing meta handling) and failure behavior unaddressed.

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 50%: x_payment is well documented in the schema, but url is only declared as a string with no format or semantics. The description does not compensate by saying url must be an absolute http/https page URL, so the coverage gap persists. Baseline 3 fits a two-parameter tool with half its params explained elsewhere.

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?

Uses a specific verb ('Extrae') plus resource ('metadata HTML') and enumerates the exact fields returned (title, meta description, canonical, favicon, Open Graph), so the agent can tell this apart from img_tools_metadata and docs_tools_pdf_metadata by the 'de una página' scope. It stops short of explicitly naming those siblings as out of scope.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The only implicit routing cue is 'de una página', which the agent must infer. Usage guidance is essentially absent.

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