Skip to main content
Glama

Compare one module across extractions

datasheetvend_compare_extractions
Read-onlyIdempotent

Compare the SAME module across 2-4 of your extraction jobs in one aligned table, instead of reading each job. Rows align on key_field (default: the pin or register identifier) and compare value_field (default: the name); pass keys for specific pins or registers. Parts are never merged: values are positional per job, and a key missing from one part is null there. A job whose outputs expired, whose module is empty or unreadable is listed with its problem, never dropped. Differences come first and differingRows counts every row, not only the returned page (totalRows beside it). Get job ids from datasheetvend_search_my_extractions. 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_ids": "<job_ids>",
      "module": "<module>"
    },
    "name": "datasheetvend_compare_extractions"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNoOnly these keys, for example ['1','2','A1'].
limitNoRows returned, differences first. Default 30.
moduleYesThe module to compare, for example pinout, register_map, absolute_max.
job_idsYes2-4 extraction jobs in your account.
key_fieldNoField to align rows on, for example 'pin_number'.
value_fieldNoField whose values are compared, for example 'pin_name'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: nothing is extracted, no model is called, no credits are consumed, failed/expired jobs are listed with their problem rather than dropped, and parts are never merged (positional values, null for missing keys).

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?

A single dense paragraph that is front-loaded with the core action and scope, then layers constraints, failure handling, and cost. Every sentence carries information an agent needs; nothing is redundant with the title or schema.

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

Completeness4/5

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

With no output schema, the description does the work of explaining the return shape: an aligned table, differences first, differingRows counting all rows versus totalRows, and nulls for missing keys. That covers what an agent needs to interpret results, though it could say more about the per-job problem listing format.

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 100%, so the baseline is 3, but the description adds defaults not present in the schema (key_field defaults to pin/register identifier, value_field defaults to the name) and explains that `keys` targets specific pins or registers. It does not explain limit's interaction beyond what the schema says, keeping it short of a 5.

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: compare the SAME module across 2-4 extraction jobs in one aligned table. It explicitly contrasts with the alternative behavior (reading each job) and names the sibling that supplies job ids, so an agent can distinguish it from datasheetvend_search_my_extractions.

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?

Gives clear when-to-use framing ('instead of reading each job'), the prerequisite for job ids (datasheetvend_search_my_extractions), the ownership constraint (owner or TEAM-shared, refunded job refused), and the API key requirement. Little 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources