Skip to main content
Glama

Get company details

crunch_get_company_details
Read-only

Retrieve a Crunch company's name, number, VAT registration and scheme, and business and registered addresses to verify details and support accounting tasks.

Instructions

Get the business's details from Crunch: company name and number, VAT registration number, current VAT scheme (for example flat rate, with industry and limited cost trader status), and business and registered addresses.

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_get_company_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full objects from the API instead of compact summaries (larger)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/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 the read-only nature is covered. The description adds the returned data set, which is useful since there is no output schema, but it says nothing about the API call's cost, authentication flow, or why the tool is marked non-idempotent.

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?

A single front-loaded sentence with every clause carrying content (the field list is the main payload), and no filler or repetition of the title. The parenthetical examples on the VAT scheme are dense but earn their space.

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 and a single optional parameter, the description's field enumeration is the main source of return-value information, and it covers the important fields. Missing only usage context and any auth prerequisite, which keeps it from a 5.

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% for the single 'raw' parameter, whose description already explains it returns full API objects instead of compact summaries. The tool description adds no meaning about how or when to set raw, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Get the business's details from Crunch') and enumerates the returned fields (company name/number, VAT registration number, VAT scheme, addresses), which distinguishes it from the user-details sibling. It stops short of explicitly naming the sibling, so not a 5.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as authentication, and no pointer to alternatives like crunch_get_user_details or crunch_get_vat_summary. The agent must infer usage from the purpose alone.

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