Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Fetch one Deals deal or note by id

fetch
Read-only

Resolve one id returned by search (a 'deal:' or 'note:') back to its full record: { id, title, text, url, metadata }. An unrecognized id, or a note id on an unbound connection, answers { error: 'unknown_id' }. For clients that only speak search/fetch (e.g. ChatGPT's chat connector mode).

Input Schema

NameRequiredDescriptionDefault
idYesAn id returned by search.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive and open-world, so the bar is lower; the description still adds the concrete return shape {id, title, text, url, metadata} and the 'unknown_id' error including the unbound-connection edge case for note ids. It does not explain how the `person` and `project` scoping parameters affect resolution.

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?

Three compact sentences: identity of the resource, its namespaced input format, the return/error contract, then the client-compatibility caveat. No restatement of the title and nothing wasted.

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?

No output schema exists, and the description compensates by spelling out the record fields and the error payload shape. The only gaps are the optional person/project scoping behavior for a tool that can run as a different holder or workspace.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning beyond the schema's generic 'An id returned by search' by specifying the 'deal:<id>'/'note:<id>' prefix formats and what an unrecognized id yields. The optional person/project parameters receive no semantic elaboration in the description.

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 ('Resolve one id returned by search back to its full record') and pins the id namespace to 'deal:<id>' or 'note:<id>'. The closing sentence distinguishes it from the general toolbox path by naming the search/fetch-only client mode, which no sibling (e.g. connections_note_get, connections_deals_list) covers.

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

Usage Guidelines4/5

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

Explicitly says the id must come from `search` and that this tool exists for clients limited to search/fetch, which gives a clear use condition. It stops short of saying when an agent with full tool access should prefer a richer sibling instead, so the exclusion side is only implied.

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

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