Skip to main content
Glama

Search your extractions

datasheetvend_search_my_extractions
Read-onlyIdempotent

Find your own (non-archived) extraction jobs by condition: filename words, a module that produced output, jobs with warnings, or jobs waiting on a decision. Returns job ids, status, warning counts and which modules hold output, never module data: pass an id to the other tools (datasheetvend_explain_warnings, datasheetvend_compare_extractions, datasheetvend_search_document) or read GET /api/v1/jobs/{id}/. totalMatched is counted after every filter: exact when scanComplete is true, otherwise a stated floor over the newest jobs scanned (countingNote). An empty list is a real answer. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datasheetvend_search_my_extractions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoJobs returned, newest first. Default 10.
moduleNoOnly jobs where this module produced output.
filename_containsNoWords in the datasheet filename.
only_with_warningsNoOnly jobs whose extraction raised at least one warning.
only_needing_reviewNoOnly jobs waiting on a decision of yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, yet the description still adds material context: nothing is extracted, no model is called, no credits are consumed, refunded jobs are refused, and access is limited to your own or TEAM-shared jobs. It also discloses the subtle counting behavior (exact when scanComplete is true, otherwise a floor with countingNote), which is genuinely beyond the annotations. It stops short of describing the response envelope in detail, keeping it just under a 5.

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 purpose and filters before the behavioral caveats, and every clause carries information (cost, access, counting semantics). It is dense — long multi-clause sentences with parentheticals — which slows parsing slightly, but there is no filler to cut.

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 five-parameter read-only search with no output schema, the description covers what is returned (job ids, status, warning counts, which modules hold output), the exactness caveat on totalMatched, cost, auth requirement and access scoping. Nothing an agent needs in order to call and interpret it correctly is missing.

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 description coverage is 100%, so each parameter is already fully documented, including the module enum and the 1-25 limit. The description adds only that totalMatched is computed after every filter and that limit applies 'newest first' — useful but modest added meaning over the schema.

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 ('Find') and a precisely scoped resource ('your own (non-archived) extraction jobs'), then enumerates the four filter conditions the tool supports. It also explicitly contrasts itself with datasheetvend_explain_warnings, datasheetvend_compare_extractions and datasheetvend_search_document by declaring it returns 'never module data', so an agent can separate it from siblings without opening schemas.

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?

Routes the agent explicitly: use this to locate jobs, then pass an id to the named sibling tools or to GET /api/v1/jobs/{id}/<module> for the data itself. It also pre-empts a common misread with 'An empty list is a real answer' and states the access condition (owner, or TEAM-shared; refunded jobs refused).

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