Skip to main content
Glama

Find the same records in other systems

find_linked_records
Read-onlyIdempotent

AI Agents: Use for questions across systems, such as which won deals have no invoice yet: for up to 50 records it returns the same records in the customer's other systems, as their syncs link them. Not for links inside one system (use list_related_records).

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": {
      "system": "<system>",
      "type": "<type>",
      "ids": "<ids>"
    },
    "name": "find_linked_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesThe ids of the records, at most 50.
typeYesThe record type, such as contact or invoice.
systemYesThe AI agent: its system or connection name.

Output Schema

NameRequiredDescriptionDefault
typeYes
noticeNo
recordsYes
systemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / system / description
      Previous value: -"Which AI agent: the system's id from get_ai_agent_options, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"The AI agent: its system or connection name."
    • changedInput schema / properties / type / description
      Previous value: -"The record type, as get_ai_agent_options lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, such as contact or invoice."
  2. Changed2 schema fields changed
    • changedInput schema / properties / system / description
      Previous value: -"Which AI agent: the system's id from get_ai_agents_info, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"Which AI agent: the system's id from get_ai_agent_options, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."
    • changedInput schema / properties / type / description
      Previous value: -"The record type, as get_ai_agents_info lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, as get_ai_agent_options lists it: contact, opportunity, invoice, estimate, job, appointment."
  3. Changed2 schema fields changed
    • changedInput schema / properties / system / description
      Previous value: -"Which AI agent: the system's id from list_ai_systems, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"Which AI agent: the system's id from get_ai_agents_info, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."
    • changedInput schema / properties / type / description
      Previous value: -"The record type, as list_ai_systems lists it: contact, opportunity, invoice, estimate, job, appointment."New value: +"The record type, as get_ai_agents_info lists it: contact, opportunity, invoice, estimate, job, appointment."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the description's job is lighter. It still adds meaningful context by explaining that results depend on existing sync-created links across systems, which tells the agent results may be empty for unsynced records. It does not state what happens for records without links or whether the 50-record limit is enforced per call.

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 dense sentence that front-loads the use case, then the return behavior, then the exclusion. The 'AI Agents:' prefix is slightly awkward framing but costs little; no sentence is filler.

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?

With a full output schema, complete parameter documentation and rich annotations, the description supplies what structured fields cannot: the cross-system question framing and the boundary against list_related_records. Minor gaps remain around empty-link results and how sync-established links are scoped, but nothing critical to calling it correctly is missing.

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 all three parameters (system, type, ids) are already documented with descriptions. The description only restates the 50-record cap already expressed by maxItems in the schema and adds no new meaning about id format or how 'system' names are resolved. Baseline 3 is appropriate when the schema carries the semantics.

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?

States a specific verb and resource and defines the scope precisely: it returns 'the same records in the customer's other systems, as their syncs link them.' It also names the sibling it is not (list_related_records), so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('questions across systems, such as which won deals have no invoice yet') and an explicit exclusion with the alternative named: 'Not for links inside one system (use list_related_records).' When-to-use and when-not-to-use are both covered.

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