Skip to main content
Glama

Connections clean-up summary

connections_summary
Read-only

Returns connection counts by tier, reason, state, and level, plus queue size, daily caps, last removal and warning, and halt status. Reads local files only.

Instructions

Returns counts by tier, reason, state and level, the queue (spam and borderline rows with a URL and no state), today and this sitting against their caps, the last removal and warning, days since the warning, and whether the halt file exists. It reads local files only.

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": "connections_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the tool reads local files only, and it discloses the exact shape of what is computed, including cap-relative figures and the halt-file check. No output schema exists, so this return-value disclosure carries real weight.

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 front-loaded sentence opening with the verb 'Returns', followed by a compact scoping note. The enumeration is long but each item is informative given the absence of an output schema; nothing 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?

For a zero-parameter, read-only status tool with no output schema, the description covers the returned fields in considerable detail and clarifies the data source (local files). Minor gaps remain: it doesn't say what happens when the halt file or data files are absent, or whether stale data is possible.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is required and spends its space on outputs instead, which is the right allocation.

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?

States a specific verb and resource — returns aggregate counts and status for the connections clean-up pipeline — and enumerates the exact dimensions (tier, reason, state, level, queue, caps, last removal/warning, halt file). An agent can tell this is a read-only overview tool rather than a per-row listing like connections_list, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no named alternative (e.g., connections_check or connections_list) to route against. The enumerated return contents only weakly imply 'use this to get a status overview before acting'.

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