Skip to main content
Glama

GTM Daily

Related records

get_gtm_related_records
Read-onlyIdempotent

Typed, data-grounded links between public records: tool to public jobs mentioning it, tool to approved resources, job to its tools and similar jobs, creator to their published work, launch to its listing.

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": {
      "entity_type": "<entity_type>",
      "id": "<id>"
    },
    "name": "get_gtm_related_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNoMax results (default 10, max 50).
entity_typeYes

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
dataNo
statusYes
messageNo
warningsNo
next_stepNo
next_cursorNo
action_grantNo
approval_urlNo
correlation_idYes
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description does not need to repeat safety details. It adds useful context by calling the links 'typed' and 'data-grounded', but it does not describe ordering, pagination, missing-record behavior, or result shape beyond what annotations and the output schema provide.

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?

The definition is a single front-loaded sentence that earns most of its length by enumerating the supported relationship types. It avoids repetition of annotation or schema fields, though the colon-and-semicolon list is dense and could be slightly easier to scan.

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?

For a read-only related-records endpoint with an output schema, the description covers the key entity-to-relationship mapping and is sufficient to call the tool correctly. The main remaining gap is the meaning/format of the id parameter, which is mitigated by the required field name and the output schema.

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 only 33%, so the description must compensate for undocumented parameters. It does add meaningful semantics for entity_type by mapping each enum value to its relationship types, but it says nothing about the required id parameter's format or meaning beyond the obvious record identifier.

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 clearly identifies the resource as typed links between public records and enumerates the concrete relationship types for each entity. It is distinguishable from sibling entity-fetch tools like get_gtm_tool or get_job_details, though the opening phrasing is more conceptual than an explicit verb such as 'returns related records'.

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 relationship list implies when the tool is useful: when an agent needs connections around a tool, job, creator, or launch. However, it does not explicitly say when to choose this over fetching the entity directly or using sibling search/profile tools, and it gives no exclusions or alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources