Skip to main content
Glama

HonestCRM

Get a company

get_company
Read-onlyIdempotent

Read one company with its contacts, open deals, 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_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description's real contribution is disclosing the returned payload shape (embedded contacts, open deals, open tasks, last 5 activities), but it omits how those embedded collections are bounded or truncated (e.g., are contacts/deals paginated?), which matters given there is no output schema.

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 that names the operation first and the returned sub-resources second. Every clause carries information; only slight cost is that the payload list is packed into one breath without structure.

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, describing the return contents is essential and this definition does so, including the notable "open" and "last 5" qualifiers. It falls short only on bounding/pagination behavior for the embedded collections and on error behavior for a missing company.

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?

There is a single parameter at 100% schema description coverage, which sets the baseline at 3. The description adds no meaning beyond the schema — it does not clarify id format, lookup behavior, or error handling for unknown ids.

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 ("Read one company") and enumerates the included sub-resources (contacts, open deals, open tasks, last 5 activities). This clearly distinguishes a single-record fetch from list/search siblings, though it doesn't name them explicitly.

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?

No when-to-use or when-not-to-use guidance, and no mention of prerequisites such as needing a valid company id or what happens when the id is unknown. The only implied guidance is that "one company" means a single-record read rather than a listing.

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