Skip to main content
Glama

HonestCRM

Search contacts, companies and deals

search
Read-onlyIdempotent

Find contacts, companies and deals by name, email, phone, domain or title.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results per type. Default 10, at most 25.
queryYesText to look for.
typesNoLimit the search to these record types. Default: all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond annotations the description only adds the set of fields matched, and says nothing about ordering, result counts, or behavior with ambiguous matches.

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?

A single front-loaded sentence with no filler; every clause carries information about scope or matching fields. Nothing is repeated from the title beyond what adds precision.

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?

This is a simple, fully annotated, fully documented three-parameter read tool, and the description covers scope and matching semantics. The remaining gap is minor: no note on result ordering or on the no-output-schema return shape, which an agent might want when interpreting hits.

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

Parameters4/5

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

Schema coverage is 100%, so limit and types are already documented, and the baseline is 3. The description earns a bump by clarifying what the query string actually matches against (name, email, phone, domain, title), which the schema's bare 'Text to look for' does not convey.

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 uses a specific verb, 'Find', plus the three resources it spans (contacts, companies, deals) and the matchable fields (name, email, phone, domain, title). That is enough to separate it from single-record siblings like get_contact or get_deal, though it never explicitly says how it differs from list_deals.

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: the reader infers this is the text-lookup entry point versus the get_*/list_* tools. There is no explicit when-to-use, when-not-to-use, or named alternative, and no guidance on what to do when a search returns nothing.

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