Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

get_contact_details

Read-only

Retrieve complete contact details by contact ID to view or verify a person's information in Offorte.

Instructions

Get all details for a contact by id

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1
  2. Removed
  3. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds nothing: it doesn't say what 'all details' includes, what happens if the id is unknown (error vs empty), or whether the lookup crosses workspace boundaries despite being open-world.

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?

A single eight-word sentence with the resource and lookup key front-loaded; nothing is wasted. It is arguably too terse rather than too verbose.

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?

This is a simple read tool with no output schema, so the description doesn't need to explain return values. However, 'all details' is left undefined, and for an open-world lookup the agent gets no sense of scope or failure behavior.

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 0%, but the schema is a single unconstrained string, and the description's 'by id' confirms contact_id is an identifier rather than a name. That is minimal added meaning for a one-parameter tool, so a mid score is warranted.

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 states a specific verb and resource ('Get all details for a contact') and names the key input ('by id'), which separates it from search_contact_people and create_contact. It stops short of explicitly contrasting with siblings, so it lands at 4 rather than 5.

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 guidance on when to use this versus search_contact_people or get_initial_context, and no mention of prerequisites such as needing a known contact_id. The agent must infer usage entirely from the name and the single required parameter.

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