Skip to main content
Glama

HonestCRM

Get a deal

get_deal
Read-onlyIdempotent

Read one deal with its stage, company, primary contact, open tasks and last 5 activities.

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": {
      "id": "<id>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the deal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish a read-only, idempotent, non-destructive operation. Beyond that, the description discloses the assembled related data and two useful scoping behaviors: only open tasks are included and activities are limited to the last five.

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?

The single sentence is front-loaded with the operation and singular resource, then efficiently lists the returned context and activity limit. Every phrase contributes useful selection or result information, with no filler or redundancy.

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, the schema and annotations cover invocation and safety, while the description provides a valuable result overview despite the absence of an output schema. It could be more complete by explaining how to obtain the ID and whether related resources are returned as embedded objects or identifiers, but neither gap prevents a correct call.

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%, and the schema already defines the required id as the deal's UUID. The description reinforces single-record retrieval but adds no further parameter syntax, sourcing, or validation guidance, so the high-coverage baseline 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?

The description pairs a clear verb and resource ("Read one deal") with a specific set of included data: stage, company, primary contact, open tasks, and recent activities. The singular scope and detail bundle help distinguish it from listing or other-resource tools, but no sibling is explicitly contrasted.

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?

The wording implies that this is for retrieving a known deal's consolidated details rather than browsing multiple deals. It does not explicitly say to use it when an ID is known or direct agents to list_deals or search when they still need to identify the deal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources