Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Report what Connections is missing

connections_report_missing
Idempotent

File one request for something Connections could not do, so its builders see it: it creates a task on the Connections team's board (tagged member-request) recording what the member asked for, what was missing and which tools were tried, under the member's account id and workspace, never their email. Returns the task id; the same gap from the same member within a day returns the existing task id, and a member can file up to 20 reports a day. Call it when the member's request could not be done with the available tools and they want the gap reported.

Input Schema

NameRequiredDescriptionDefault
askedYesWhat the member wanted to do, in a sentence or two.
triedNoTools or steps already tried (optional).
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
missingYesWhat Connections lacks to do it, one short item each (max 20).
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. Added

TDQS

A4.4/5.0
Behavior5/5

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

Far beyond the annotations: it discloses the destination board and member-request tag, that only account id/workspace are stored and never email, a one-day dedup that returns the existing task id, and a 20-per-day per-member cap. The annotations cover safety hints, but these operational specifics are exactly the extra context that matters for a write tool.

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?

Purpose is front-loaded and every clause carries information (dedup, rate limit, PII rule, trigger). It is dense and runs long in a single breath, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still states the return value (task id) and even the dedup return case, plus rate limits and PII handling. An agent has everything needed to call this correctly.

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 five parameters are already documented, making 3 the baseline. The description adds marginal meaning by clarifying that the filing happens under the member's account id and workspace and explicitly excludes email, but it does not explain 'asked' vs 'missing' vs 'tried' beyond what the schema says.

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+resource: files a request / creates a task on the Connections team's board tagged member-request, recording the gap. No sibling does anything similar, and the description makes that scope unmistakable.

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?

Explicit trigger: 'Call it when the member's request could not be done with the available tools and they want the gap reported,' which also implies the when-not (nothing missing, member doesn't want it filed). No alternative sibling is named, but none exists.

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