extract_pdf
Extract text + metadata from a PDF URL (text-based PDFs). (content; $0.01/call in USDC via x402, 20 free/day).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Target URL or hostname. | |
| max_pages | No |
fetcher
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses cost ($0.01/call), free tier (20/day), and type of PDF supported. However, with no annotations, it lacks details on error handling, rate limits beyond free tier, and output format. Adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with core purpose followed by pricing in parentheses. Front-loaded and efficient with no unnecessary words.
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?
Minimally adequate for a simple tool: explains purpose, type, and cost. Lacks details on output, error behavior, and page limit parameter. Average completeness given 2 parameters and no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50% (only 'url' has a generic description). The description adds no information about parameters beyond the schema, failing to compensate for the low coverage especially for 'max_pages'.
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?
Clearly states verb 'Extract' and resource 'PDF URL', with qualifier 'text-based PDFs' to distinguish from scanned PDFs. Differs from sibling 'extract_content' which targets web pages.
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?
No explicit guidance on when to use this tool versus alternatives like 'extract_content'. The qualifier 'text-based PDFs' implies limitations but does not address when not to use or mention other sibling tools.
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.
TDQS
B3.4/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but there are overlapping pairs: unfurl_url/get_oembed/find_favicon all provide URL metadata, and render_page/screenshot_page both render a page (render_page can also screenshot). Descriptions help disambiguate, so only minor confusion is likely.
Naming Consistency3/5
Tool names mix verb_noun patterns (check_domain, extract_content) with noun_verb patterns (dns_lookup, ssl_lookup, whois_lookup). Additionally, guard_inspect and guard_tx deviate from the typical verb-first style. The naming is readable but not consistent.
Tool Count3/5
With 19 tools, the server is at the heavier end of the scale. While it covers a broad web-intel toolkit, several tools feel out of place for a 'fetcher' (e.g., generate_qr, guard_tx, guard_inspect), making the set feel bloated and unfocused.
Completeness4/5
The core web-fetching and analysis surface is well covered: DNS, WHOIS, SSL, headers, content extraction, rendering, screenshots, feeds, embeds, redirects, and robots. Missing is a simple raw HTML fetcher, but extract_content and render_page likely cover most needs. The addition of security and utility tools doesn't fill obvious gaps.