Skip to main content
Glama
Sign In

OsmO AI Receptionist

by app.getosmo
OverviewDiscussionsAdmin

Search Contacts

search_contacts
Read-only

Searches the user's phone book (the contacts synced from their phone) by the start of a name. Each match has the name and full number. It covers people who are not in the call history. 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": {
      "query": "<query>"
    },
    "name": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most 10; default 5.
queryYesThe start of the name, e.g. "Ravi".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the closing 'Read-only' sentence mostly restates structured data. The description does add genuine behavior beyond annotations: prefix-only matching and that each match returns a name with the full number, which is useful 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?

Three short sentences with the matching rule front-loaded and no wasted clauses. The trailing 'Read-only' overlaps the annotations, a minor 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 simple two-parameter read tool with no output schema, the description supplies the missing return-shape information ('name and full number') and the matching semantics. Only result ordering and the cap of 10 matches are left to the schema, which is acceptable.

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 coverage is 100%, so the schema already documents both 'query' and 'limit' with bounds. The description reinforces that query is a name prefix rather than a substring, but adds no syntax or format detail the schema lacks, and never mentions the limit parameter.

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 ('Searches the user's phone book') plus the matching rule ('by the start of a name') and the scope ('contacts synced from their phone'). It partially differentiates from siblings by noting it covers people not in the call history, though it never contrasts with find_contact or find_business by name.

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 clause 'covers people who are not in the call history' implies when this tool is needed rather than stating it, and no alternative tool is named as the fallback for call-history lookups. Usage is inferable but not explicit.

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

All OsmO AI Receptionist toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources