Skip to main content
Glama

get_required_permissions

Read-only

Which exchange API key permissions a trading bot needs, and which to leave off, with the exchange's own source link. Full guide: https://quantaira.app/api-key-safety-checker. Read-only; takes no keys.

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": {
      "exchange": "<exchange>"
    },
    "name": "get_required_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
bot_typeNoWhat the bot does
exchangeYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description usefully reinforces this with 'takes no keys' – a meaningful assurance for a credential-safety tool that nothing secret must be supplied. It also discloses provenance (the exchange's own source link) and points to an external guide, adding context the annotations do not carry. It does not describe response size or structure, but with no output schema that is a minor omission rather than a contradiction.

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 compact sentences plus a reference URL, with the core purpose front-loaded and the safety reassurance placed last. The opening is a noun fragment rather than a full clause, but nothing is wasted or buried.

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?

For a two-parameter, read-only lookup with no output schema, the description covers what it returns, where the answer comes from, and that no credentials are needed. The main residual gap is behavior when the optional bot_type is not supplied, which an agent would need to know before calling.

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?

At 50% schema description coverage, only bot_type carries a schema description ('What the bot does'), while exchange has none. The description mentions both concepts ('exchange API key permissions', 'trading bot') but never explains the bot_type enum choices or what happens if the optional bot_type is omitted, so it only partially compensates for the coverage gap.

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 uses a specific framing – 'Which exchange API key permissions a trading bot needs, and which to leave off' – which tells an agent exactly what is returned (a recommended permission allow/deny list keyed on exchange and bot type). It is clearly distinct from safety-checklist or red-flag siblings, though it never names those siblings explicitly.

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 implied: this is the tool to call when configuring an API key for a bot on a given exchange. There is no explicit statement of when to prefer a sibling (e.g., get_safe_key_checklist or get_red_flags) or when the tool is not appropriate, leaving routing to inference.

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