Skip to main content
Glama

Read a hardware datasheet

draft_hardware_from_datasheet

Reads a part's datasheet (a public https link, or pasted text) and drafts its catalog entry and exact dimensions. Every number is checked against a quoted line of the source, and nothing is saved. Review it with the user, then confirm with confirm_hardware_dimensions. Needs a connected Printlooper account.

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": "draft_hardware_from_datasheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only flag openWorldHint and non-read-only; the description adds real context: every number is verified against a quoted source line, nothing is persisted, and a connected Printlooper account is required. The phrase 'nothing is saved' sits slightly in tension with readOnlyHint=false, but readOnlyHint=false is a permissive hint rather than a claim of mutation, so this reads as clarifying scoping rather than a contradiction.

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?

Four short sentences, each doing distinct work: purpose, verification/no-save guarantee, review-and-confirm workflow, and the account prerequisite. Front-loaded and free of filler.

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?

No output schema exists, and the description still conveys what comes back (a catalog entry with exact dimensions) and that the result is provisional. Minor gaps remain around what happens with zero inputs or a failed fetch, but the essentials for correct invocation are present.

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 coverage is 0%, so the description carries the burden. It usefully explains that the url parameter must be a public https link and that text is pasted content, but it does not say whether both can be supplied, what happens if neither is, or address the size limits encoded in 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?

Specific verb and resource: reads a datasheet from a link or pasted text and drafts a catalog entry plus exact dimensions. It also implicitly distinguishes itself from confirm_hardware_dimensions by naming that tool as the next step, so the agent can tell drafting apart from committing.

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?

Clear workflow guidance: do the draft, review it with the user, then confirm via confirm_hardware_dimensions. It does not explicitly rule out other catalog-entry paths among siblings, but the when-to-use context and the required follow-up are stated plainly.

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