Skip to main content
Glama

Get supplier

crunch_get_supplier
Read-only

Retrieve complete supplier details by supplier ID to view and verify supplier records in Crunch accounting.

Instructions

Get a supplier in full.

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": {
      "supplier_id": "<supplier_id>"
    },
    "name": "crunch_get_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
supplier_idYesSupplier ID (see crunch_list_suppliers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing about what "in full" returns, whether missing IDs error or return empty, or why idempotentHint is false on a read - the one behavior worth clarifying is left untouched.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with zero filler, which is structurally fine. The brevity is under-specification rather than efficiency - nothing an agent needs is actually conveyed.

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

Completeness3/5

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

For a one-parameter read tool with full schema coverage and read-only annotations, the structured fields carry most of the load. However, no output schema exists and the description never indicates what a full supplier record includes, so a small but real gap remains.

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 100% and the single parameter is documented in the schema itself, including a cross-reference to crunch_list_suppliers. The description adds no meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get a supplier in full" restates the tool name and title almost verbatim; the only added signal is the vague qualifier "in full." It does not say what a supplier record contains or how it differs from crunch_list_suppliers beyond implying a single detailed record.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no explicit alternative is named. An agent must infer from the name alone that this is the single-record counterpart to crunch_list_suppliers.

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