Skip to main content
Glama

Cnamio

List connections

list_connections
Read-only

Recent connections of the application, newest first, optionally for one domain or status. Needs the application credentials (not a session token).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
domainNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds what annotations cannot: the ordering (newest first) and the auth requirement that application credentials rather than a session token are needed — a genuine pre-call constraint. It omits how 'recent' is bounded and any pagination behavior.

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?

Two short sentences, no filler. Ordering and optional filters come first, then the auth prerequisite — the most likely cause of a failed call is front-loaded last but still within a single compact line.

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?

For a simple three-optional-parameter list tool with no output schema, the description covers filters, ordering and auth. It still leaves the definition of 'recent', the default result size, and the shape of returned connection records unstated, which matters since there is no output schema to fall back on.

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 0%, so the description must carry meaning. It clarifies that domain and status are optional single-value filters, but says nothing about limit (schema default 20, max 100) or what 'recent' means in time terms. Two of three parameters get some added meaning; the third gets none.

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 names the resource (connections) and the scope (recent, newest first, filtered optionally by domain or status), which is enough to distinguish it from the singular get_connection_status sibling. It stops short of an explicit verb-and-sibling contrast, so a 4 rather than a 5.

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?

It gives filtering conditions ('optionally for one domain or status') and a prerequisite (application credentials, not a session token), which is real usage context. But it never says when to choose this over get_connection_status or check_domain, so the alternative-selection guidance is only implied.

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