Skip to main content
Glama
Sign In

Outcomet

by app.outcomet
OverviewDiscussionsAdmin

Get Contact

contact_get
Read-onlyIdempotent

Fetches one tenant-scoped contact summary with compact network source labels and tags 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": {
      "contactId": "<contactId>"
    },
    "name": "contact_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdYesStable contact UUID.

Output Schema

NameRequiredDescriptionDefault
contactYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context about scope ('tenant-scoped') and content ('compact network source labels and tags'), but does not clarify error behavior or edge cases (e.g., not found). With annotations covering the safety profile and an output schema defining the return shape, a 3 is appropriate.

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?

The description is one concise sentence with zero wasted words, front-loading the verb and key scope. Every phrase ('tenant-scoped', 'compact network source labels and tags', 'by ID') contributes to selection or expectation setting.

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?

Given the simplicity of the tool (one required UUID parameter), the presence of annotations covering safety, and an output schema, the description is nearly complete. It could optionally mention error handling for missing contacts, but that is a minor gap against an otherwise sufficient definition.

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%, and the single contactId parameter is fully documented as a stable UUID in the schema. The description reinforces 'by ID' but adds no format, validation, or semantics beyond what the schema already provides. Baseline 3 applies when the schema does the heavy lifting.

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 ('Fetches'), resource ('one tenant-scoped contact summary'), and qualifier ('by ID'), which clearly differentiates it from contact_search and contact_create/update. It does not explicitly name the most relevant sibling, contact_search, but the 'by ID' phrasing makes the distinction clear enough for an agent.

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 implied: use this tool when you have a contact UUID and need a single contact. There is no explicit when-to-use guidance, no exclusions (e.g., 'use contact_search to find by name'), and no mention of alternatives. This is adequate but leaves the agent to infer the boundary with contact_search.

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

All Outcomet 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