Ask GorillaDesk (gorilladesk-mcp)

get_customer

Read-onlyIdempotent

Retrieve a specific customer's details by ID to quickly access their profile and account information in GorillaDesk.

Instructions

Fetch one customer by id. Prefer find_customer first.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "get_customer"
  }
}

Input Schema

Name	Required	Description	Default
`include`	No
`customer_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds minimal behavioral context ('prefer find_customer first'), but does not disclose anything about missing IDs, response format, or the 'include' parameter. It is adequate but not rich.

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?

Two short sentences with no filler. Efficiently communicates purpose and usage priority in minimal words.

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?

With an output schema and strong annotations, the description is sufficient for the basic fetch functionality, but the 'include' parameter remains unexplained and there is no guidance on edge cases. The usage note about find_customer adds context, but the tool description leaves some gaps around parameter behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only mentions 'by id' (mapping to customer_id) without explaining the 'include' parameter. The schema provides types/defaults but not semantic meaning, and the description fails to compensate for the missing entirely undocumented parameter.

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?

The description clearly states the tool 'Fetch one customer by id' – a specific verb and resource. It distinguishes from sibling tools like find_customer and search_customers by specifying a direct ID-based fetch.

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

Usage Guidelines5/5

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

Explicitly says 'Prefer find_customer first,' providing a direct alternative and indicating when to use this tool as a fallback. This is clear usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.