Skip to main content
Glama

Explain an extraction's warnings

datasheetvend_explain_warnings
Read-onlyIdempotent

Report the warnings an extraction raised, grouped and ranked by DatasheetVend's own classifier (the grouper the result page's warnings panel uses). Use it before trusting an extraction. Report BOTH counts: issues (distinct problems) and findings (occurrences). Use the severity given (critical, review, info); an info group or one marked internal is a pipeline note, not a problem with the part, and highSignal groups (contradictions, incompleteness) go first. severityBasis says what the severity rests on. Zero warnings is a complete answer. At most 20 groups are listed; groupsTotal says how many exist. Reads the recorded state of your account's own jobs (owner, or TEAM-shared in your workspace; a refunded job is refused): nothing is extracted and no model is called. Costs no credits. Needs a DatasheetVend API key.

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": {
      "job_id": "<job_id>"
    },
    "name": "datasheetvend_explain_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesAn extraction job in your account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses the access scope (your account's own jobs, owner or TEAM-shared, refunded jobs refused), the fact that no extraction runs and no model is called, that it costs no credits, and that an API key is needed. It also explains how to interpret the output (severity semantics, info and internal groups, highSignal ordering, the 20-group cap against groupsTotal). This is the level of behavioral detail an agent needs before calling a job-scoped read.

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 description is a single dense paragraph, but the key point (report the warnings, grouped and ranked) comes first, and the rest is operational detail: how to read counts, severity, and groups. Nearly every clause earns its place. It is close to overloaded, though, and splitting the access-and-cost facts out would improve readability.

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?

There is no output schema and only one parameter, so the description carries the return-shape burden itself; it does this well by explaining both counts (issues versus findings), severity levels and their basis, the group cap, and groupsTotal. It also covers authentication, cost, and whose state is read. Nothing an agent needs in order to call this tool 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 already 100%, and the schema describes job_id only as 'An extraction job in your account.' The description adds meaning the schema does not: which jobs are eligible (owner or TEAM-shared within the workspace) and that refunded jobs are refused. With only one parameter, this is meaningful compensation, although it doesn't give an ID format or example.

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?

The description states a specific verb and resource: report the warnings an extraction raised, grouped and ranked by DatasheetVend's classifier. It adds detail about what the grouping means (the same grouper the result page's warnings panel uses), so the agent knows exactly what it gets. It is clear, though it never explicitly contrasts itself with the sibling diagnose_extraction, so the agent has to infer that this tool reports warnings while that one diagnoses.

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

Usage Guidelines4/5

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

The description gives a clear timing instruction: use it before trusting an extraction. It also pre-empts a common failure mode by saying that zero warnings is a complete answer and by stating the job ownership and refund conditions. It does not name any alternative tool or say when not to use this one, so the usage guidance is strong context but has no exclusions.

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