Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Whistleblowing statistics

whistleblowing_stats
Read-onlyIdempotent

Counts of the channel's reports by status and category, how many got feedback in time, and the average days to first feedback, for a year or all time. No content. Free.

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

Input Schema

NameRequiredDescriptionDefault
yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it read-only, idempotent, and non-destructive, so the safety profile is covered. Beyond that, the description adds that results are aggregates with no report content and that the call is free, which is useful cost/scope context an agent would not otherwise have.

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 with the metric list front-loaded and the scope/cost caveats trailing. Every clause carries information; nothing is repeated from the annotations or schema.

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 no output schema, the description carries the return-value burden and does list the metrics returned. It stops short of describing the shape of the breakdown (e.g., how status/category counts are keyed), but it is sufficient for an agent to decide to call it.

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 0% and the single 'year' parameter is undocumented in the schema. The phrase 'for a year or all time' compensates by implying that omitting the parameter yields all-time figures and that the parameter scopes to a calendar year.

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?

It names the exact metrics returned (counts by status and category, feedback-in-time counts, average days to first feedback), which is far more specific than the title. The 'No content' phrase implicitly separates it from whistleblowing_list_reports, but no sibling is named outright.

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?

The reader can infer this is the aggregate alternative to whistleblowing_list_reports, and 'for a year or all time' hints at scoping. However, it never states when to pick this tool over the sibling list tool or what preconditions apply.

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

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