Skip to main content
Glama
Dasistaiden

whed-tools

by Dasistaiden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_extraction_schema

Returns the WHED extraction schema listing required fields with types and priorities, so the host LLM knows exactly what data to extract from scraped website content.

Instructions

Return the WHED extraction schema (REQUIRED fields only).

The host LLM should use this template to know which fields to extract
from scraped website content. Each field includes its type and priority.

Typical workflow:
  1. crawl_website / scrape_url  → get site content
  2. get_extraction_schema       → know what to extract
  3. get_db_context(domain)      → get allowed values & reference example
  4. (Host LLM extracts data)
  5. validate_profile(json)      → check the extraction
  6. save_profile(domain, json)  → persist the result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it discloses that only required fields are returned and that each field carries type and priority metadata. It is a deterministic, no-argument read tool and an output schema exists, so deeper return-format detail is unnecessary; only operational traits like caching or freshness are left unstated.

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?

The core statement is front-loaded in the first sentence, and the workflow list is compact and high-value for cross-tool routing. Step 2's gloss ('know what to extract') mildly restates the opening sentence, a small redundancy in an otherwise tight definition.

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?

For a parameterless tool with a full output schema, the description supplies everything an agent needs: what is returned, the field-level metadata attached, and where it sits in the extraction pipeline. Nothing required to call it 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?

The tool takes zero parameters and the schema description coverage is 100%, so there is nothing for the description to clarify. Baseline of 4 applies for a parameterless tool.

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 ('Return the WHED extraction schema') and adds a scoping qualifier ('REQUIRED fields only') that tells the agent what is excluded. Combined with the workflow, an agent can distinguish it from get_db_context (allowed values) and validate_profile 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?

The numbered 6-step workflow places this tool precisely in sequence between scraping and get_db_context, and states the condition for its use ('know what to extract'). Explicit alternatives and their ordering are given, so nothing 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.

Deploy Server

Other Tools