Skip to main content
Glama

Your analyses

list_analyses
Read-only

Your saved Cryptokly analyses. Free.

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": {
      "limit": "<limit>"
    },
    "name": "list_analyses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds only that results are 'saved' and 'Free'; it does not disclose pagination, ordering, authentication scope, or what is returned. With annotations covering the safety profile, this is a weak but non-contradictory contribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments are efficient and front-loaded, but the extreme brevity reflects under-specification rather than disciplined concision. 'Free' is an extra detail of unclear relevance to invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a listing tool with no output schema and an undocumented required limit parameter, the description is too sparse: it omits result ordering, pagination, and what counts as an analysis. The annotations cover read-only status but not the operational details an agent needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required limit parameter with 0% schema description coverage, and the description never mentions limit, its range, default, or pagination behavior. It therefore does not compensate for the missing schema semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as the user's saved Cryptokly analyses, which implies a listing operation. However, it never uses a verb like list or retrieve and offers no distinction from the sibling get_analysis, leaving the action recognizable only by inference from the tool name and title.

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?

It provides no when-to-use guidance, no exclusions, and no comparison to get_analysis or the other siblings. 'Free' is pricing information, not guidance about selecting this tool.

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