Skip to main content
Glama

quick_check

Free: counts of active and recent governance proposals and of contract upgrades or admin changes for one protocol, without the details. About 20 calls a minute per client.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "protocol": "<protocol>"
    },
    "name": "quick_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (default 30, max 90)
protocolYesProtocol id from /v1/protocols, e.g. aave, uniswap, lido, usdc

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?

With no annotations, the description carries the full burden and does well: it discloses the cost model ('Free:') and the rate limit ('About 20 calls a minute per client'), and clarifies that only aggregate counts, not underlying records, are returned. It does not specify the response shape or what happens if the protocol id is unknown, but the operational constraints are front and center.

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?

Two short sentences with no filler: the cost/scope distinction leads and the rate limit closes. The middle clause ('of contract upgrades or admin changes') is dense but each element corresponds to real returned data, so nothing is wasted.

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?

The tool is simple (2 params, no output schema, no annotations), and the description covers what is counted, the single-protocol scope, that details are excluded, and the rate ceiling. The only omission is any hint of the response structure or error behavior, which is minor for a counts-only endpoint.

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 both 'protocol' and 'days' (default 30, max 90) are already documented in structured form. The description reinforces that the tool is scoped to a single protocol and that results are 'active and recent', which loosely maps to the days look-back, but adds no new syntax or semantics. Baseline 3 is appropriate.

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 concrete verb ('counts') and specific resources (active/recent governance proposals, contract upgrades or admin changes) scoped to 'one protocol', and the phrase 'without the details' signals it is the summary variant rather than a detailed-report tool. It stops short of naming which sibling to use for the detailed view, so it is clear but not fully differentiated.

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?

'Free:' and 'without the details' imply this is the lightweight/triage call before reaching for a detailed tool, which is useful implied guidance. However, it never states an explicit when-to-use or when-not-to-use condition, nor does it name an alternative such as protocol_changes or protocol_digest for detail.

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