Skip to main content
Glama

get_safe_key_checklist

Read-only

10-point checklist before connecting any bot to an exchange API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed reference read; the description adds that the payload is a fixed 10-point checklist rather than a computed assessment. It does not clarify whether the checklist is static reference content or evaluated against actual state, which is the main behavioral ambiguity left.

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?

A single front-loaded sentence with no filler; the scope qualifier (10 points, pre-connection) arrives immediately. Nothing could be trimmed without losing the tool's identity.

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

Completeness3/5

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

With no parameters, no output schema, and annotations covering the safety profile, the definition is nearly complete, but with no output schema the agent is not told how the checklist is returned (list of strings, numbered items, grouped sections). For an otherwise trivial reference tool this is a small but real gap.

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 the schema needs the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless call by describing a generic pre-connection checklist with no context inputs.

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 phrase "10-point checklist before connecting any bot to an exchange API key" names a concrete artifact (a 10-item checklist) and its subject (exchange API key safety), which is enough to separate it from siblings like get_required_permissions or get_red_flags. It stops short of a clean verb+resource statement (no explicit "returns the checklist of..."), but the resource is unmistakable.

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 phrase "before connecting any bot to an exchange API key" implies the point in the workflow where this applies, which is meaningful context. It does not state when to prefer this over get_required_permissions or get_red_flags, nor any exclusions, so guidance remains inferred rather than explicit.

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