Skip to main content
Glama

Read Contact

get_contact
Read-only

Fetch detailed contact information by contact ID to look up a person's stored Microsoft 365 details for communication or follow-up.

Instructions

Get detailed contact information

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

Input Schema

NameRequiredDescriptionDefault
contact_idYesThe contact ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description carries a lighter burden, but it adds almost no extra behavior: it does not say whether a full record or a summary is returned, what a missing ID produces, or whether extra fields or permissions are involved. "Detailed" is the only hint beyond the annotation and is never clarified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded, with no wasted words. But there is no structure or detail, so the brevity comes at the cost of under-specification rather than efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read, the description is still too thin: with no output schema, the agent does not know what "detailed" means for the response or how failures are reported. Annotations cover safety, but the return-shape gap is left entirely to guessing.

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, contact_id, with 100% schema description coverage, so the schema already documents it. The description adds no format, sourcing, or identifier guidance, which is the expected baseline 3 when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get detailed contact information" names a specific verb and resource, so the agent knows it retrieves a contact record rather than creating or deleting one. But "detailed" is unquantified, and nothing distinguishes it from neighbors such as get_user or get_me.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives for looking up people versus contacts. The agent must infer everything from the name alone.

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

Deploy Server

Other Tools