Skip to main content
Glama

Get client

crunch_get_client
Read-only

Retrieve a client’s full record by ID, including contact details, billing address, payment terms, and notes.

Instructions

Get a client (customer) in full: contact details, billing address, payment terms and note.

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": {
      "client_id": "<client_id>"
    },
    "name": "crunch_get_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYesClient (customer) ID (see crunch_list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/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 safety profile is covered. The description adds genuine value by enumerating the returned fields (contact details, billing address, payment terms, note), which matters because there is no output schema, but it says nothing about not-found behavior or whether nested sub-objects are returned.

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 compact sentence with the resource and the returned contents front-loaded; nothing is padded. It could be marginally tighter, but every clause carries information.

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 one-parameter, read-only retrieval tool with no output schema, the description supplies the critical missing piece: what fields come back. Only minor gaps remain, such as error behavior for an unknown ID.

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?

Only one parameter and schema description coverage is 100%, so client_id is already fully documented in the schema including the cross-reference to crunch_list_clients. The description adds no meaning about the ID's format or source beyond that.

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?

Specific verb plus resource ("Get a client (customer)") with an explicit statement of what the record contains: contact details, billing address, payment terms, note. It is clearly distinct from aggregate siblings such as crunch_get_aged_debtors, though it does not name crunch_list_clients as the alternative within the description itself.

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?

Usage is only implied: requiring a single client_id and returning the record "in full" signals single-record lookup versus a listing call. There is no explicit when-to-use/when-not statement or pointer to an alternative tool inside the description, and the useful pointer to crunch_list_clients lives in the schema, not here.

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