Skip to main content
Glama

CON, Central Operating Network

Public rating log

rating_log
Read-only

State of CON's hash-chained public rating log: closing hash per day, entries, and how High ratings fared one hour later (misses included). With the link to the verify script.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still adds real context beyond that: the log is public and hash-chained, misses are explicitly included so the data is not survivorship-biased, and it returns a link to an external verify script. It does not disclose output size, pagination, or time coverage, which keeps it below a 5.

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 dense sentence with the resource front-loaded and the returned contents in a compact list; nothing is redundant. The trailing fragment 'With the link to the verify script.' reads awkwardly and is syntactically detached, which is the main structural flaw.

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 burden of describing returns, and it does list the three content categories plus the verification link. Read-only safety is covered by annotations. It remains slightly incomplete on granularity — how far back 'per day' goes, how many entries, and what 'CON' means — which leaves an agent without expectations about result size.

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 there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

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 a specific resource (CON's hash-chained public rating log) and enumerates what the retrieval yields: closing hash per day, entries, and one-hour-later performance of High ratings. It is distinguishable from the unrelated siblings (check_coin, define_term, launch_index, list_systems). It loses a point for lacking an explicit verb and for relying on undefined jargon like 'CON' and 'closing hash'.

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?

Usage is only implied: an agent infers it should call this when it wants the state of the rating log. There is no explicit when-to-use, when-not-to-use, or named alternative, though none of the listed siblings appear to compete with it. The 'with the link to the verify script' hint suggests a verification workflow but does not spell it out.

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