Skip to main content
Glama
Sign In
Coherence XRM

Coherence XRM

Official
by getcoherence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_outreach_item

Retrieve the full MDX content of an outreach item by providing its unique ID.

Instructions

Get a single outreach item by ID, including its full content (MDX).

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": {
      "itemId": "<itemId>"
    },
    "name": "get_outreach_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesOutreach item UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It mentions the output includes MDX content but does not disclose side effects (none expected for a read), error behavior, permissions, or rate limits. Adequate but not detailed.

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?

Single sentence of 14 words, front-loaded with verb and resource. No redundancy or filler. Efficient and clear.

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 no output schema, the description hints at response content ('full content (MDX)'). However, it could mention other typical fields (e.g., metadata). Still, for a simple single-parameter get, it is largely complete.

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?

Only one parameter 'itemId' which is described in the schema as 'Outreach item UUID'. The description adds no extra meaning; schema coverage is 100%, so baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'Get', the resource 'outreach item', and specifies that it returns full MDX content. It distinguishes itself from sibling tools like 'list_outreach_items' (which lists) and 'update_outreach_item' (which modifies).

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 description implies use for retrieving a specific item by ID, but does not explicitly state when to use this tool over alternatives like 'list_outreach_items' or 'get_record'. No guidance on prerequisites or context is provided.

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