Skip to main content
Glama

Client card

dosai_get_contact
Read-onlyIdempotent

One client: name, phones, channels, deals, tags. For the history of events use dosai_get_contact_timeline.

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": {
      "workspace_id": "<workspace_id>",
      "contact_id": "<contact_id>"
    },
    "name": "dosai_get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYes
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed2 schema fields changed
    • removedInput schema / properties / contact_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / workspace_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.6/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 and idempotency profile is covered. The description's additional value is limited to enumerating the returned fields; it says nothing about permissions, whether a missing contact errors or returns empty, or response shape. That is adequate but not rich behavior beyond annotations.

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?

Two short sentences, front-loaded with what the tool returns and ending with the sibling redirect. No filler, no 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 two-parameter, read-only lookup with no output schema, listing the returned fields plus the timeline redirect covers most of what an agent needs. The remaining gap is how a nonexistent or inaccessible contact_id behaves, which matters given required UUID inputs.

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

Parameters2/5

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

The description never mentions workspace_id or contact_id. Only workspace_id carries a schema description (pointing at dosai_list_workspaces); contact_id is documented solely by its name and uuid format. At 50% coverage the description should compensate for the gap and does not.

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 names the concrete resource ('One client') and enumerates the payload ('name, phones, channels, deals, tags'), so an agent knows exactly what comes back. It falls short of a 5 only because the retrieval verb is implied rather than stated, but the resource and scope are unambiguous against siblings like dosai_get_contact_timeline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes event-history requests to dosai_get_contact_timeline, giving a clear alternative and the condition that selects it. It offers no other exclusions (e.g., when to prefer dosai_get_lead or dosai_get_deal), so context is clear but not exhaustive.

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