Skip to main content
Glama
Sign In
Coherence XRM

Coherence XRM

Official
by getcoherence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_record

Retrieve a specific record from a module using its unique identifier. Specify the module slug and record UUID to get the record data.

Instructions

Get a single record by ID from a module.

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": {
      "moduleSlug": "<moduleSlug>",
      "recordId": "<recordId>"
    },
    "name": "get_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleSlugYesModule slug
recordIdYesRecord UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided, so the description bears full burden. It indicates a read operation but does not disclose whether the record is guaranteed to exist, permission requirements, or side effects. Acceptable for a simple get but missing details.

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?

Extremely concise single sentence with no wasted words. Front-loaded with verb and resource.

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?

With no output schema, the description could mention what is returned (e.g., the record fields). It is complete enough for a trivial get operation but lacks explicit return behavior and error handling.

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 100%, so the input schema documents both parameters. The description adds no additional semantic value beyond what 'by ID' implies. Baseline 3 applies as schema does the heavy lifting.

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 action 'Get', the resource 'single record', and the method 'by ID'. It distinguishes from sibling tools like list_records (returns multiple), create_record, and delete_record.

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?

No guidance on when to use this tool vs alternatives. The description does not mention when not to use it or provide context for selecting this over list_records or other get-like tools.

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