Skip to main content
Glama

Search contacts

contact_search
Read-onlyIdempotent

Searches contacts by a full or partial name or company. Read only.

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": {
      "q": "<q>"
    },
    "name": "contact_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch text — matches name or company
pageNo0-based page number, default 0
sizeNoPage size, default 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so 'Read only' mostly restates structured data rather than adding it. The one genuine behavioral addition is that matching works on full or partial text across name and company, though nothing is said about result ordering, empty-result behavior, or whether matching is fuzzy.

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?

Two short sentences, front-loaded with the verb and resource, with no filler. The trailing 'Read only' sentence is nearly wasted effort given the annotations, keeping it just short of a 5.

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?

For a simple three-parameter search with complete schema coverage and full annotations, the description covers the essentials of what is queried and that it is safe. It is silent on result shape and pagination behavior, and with no output schema present it could have said more about what comes back.

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%, so q, page, and size are already documented with defaults. The description's wording about name-or-company matching slightly enriches q but largely duplicates the schema's 'Search text — matches name or company', so the baseline 3 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?

States a specific verb (searches) and resource (contacts) plus the matchable fields (name or company), so an agent knows exactly what the query targets. It does not, however, distinguish itself from other lookup-style siblings such as contact_list, contact_detail, or directory, leaving the agent to infer which lookup path applies.

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 phrases 'full or partial' suggest this tool is the right choice when you have a fragment of a name or company rather than an identifier. There is no explicit when-to-use or when-not-to-use guidance and no named alternative for exact-ID lookups or enumeration.

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.