Skip to main content
Glama

List suppliers

crunch_list_suppliers
Read-only

List suppliers you buy from with their default expense type, country and VAT number. Use returned IDs when creating expenses in Crunch.

Instructions

List suppliers (who you buy from), with their default expense type, country and VAT number. name asks Crunch for an exact company name. Use the IDs when creating expenses.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full objects from the API instead of compact summaries (larger)
nameNoExact company name to look up
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value
include_archivedNoInclude archived suppliers (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the description only needs to add operational detail. It adds that `name` triggers an exact company-name lookup rather than a fuzzy one, which is genuinely useful behavior, but says nothing about pagination despite a `limit` parameter, nor about the difference between compact and full (`raw`) responses.

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?

Three short sentences, front-loaded with what the tool returns before the parameter note. Slightly terse to the point of dropping connective context ('Use the IDs when creating expenses' assumes knowledge of the expense tools), but nothing is padded.

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?

For a six-parameter, optional-only list tool with full schema coverage and annotations, the description is essentially complete: purpose, returned fields, exact-name behavior, and downstream use of IDs. The remaining gap is pagination/limit behavior and what `raw` returns, neither of which is covered by an output schema.

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 all six parameters are already documented; the baseline is 3. The one added nuance is confirming that `name` is an exact company-name lookup, which reinforces rather than extends the schema's own wording.

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 ('List suppliers') and immediately disambiguates the entity with '(who you buy from)', which separates it from the client-oriented siblings. It also names the fields carried in the response (default expense type, country, VAT number), so an agent knows what it gets without opening the schema.

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

Usage Guidelines3/5

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

'Use the IDs when creating expenses' gives downstream context, and '`name` asks Crunch for an exact company name' hints that exact-match is a distinct mode, but the description never states when to prefer `search` over `name`, or when archived records matter. Usage is implied rather than spelled out, and no alternative tool is named.

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