Skip to main content
Glama

Read the bot's tool calls

get_tool_calls
Read-onlyIdempotent

Read the bot's calls to store tools to see which tool ran, with which arguments, and whether it failed. Filter by conversation, tool name, or failures; bodies are omitted to protect credentials.

Instructions

Read the calls the bot made to the store's own tools (room availability, order status, checkout...): which tool, with which arguments, whether it failed and how. Use conversation_id to see every call behind one conversation. Request and response bodies are never returned, because they can hold credentials.

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_tool_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tool_nameNo
failed_onlyNo
conversation_idNo

Output Schema

NameRequiredDescriptionDefault
callsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: request and response bodies are redacted because they may hold credentials, which tells the agent not to expect payloads. It stops short of describing ordering, pagination, or result volume.

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?

Three sentences, no filler, with the core scope stated first and the redaction caveat last where it belongs. Every clause carries information the agent needs.

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?

An output schema exists, so return shape need not be explained, and the description still covers scope, redaction, and the main filter. The only real omission is the limit parameter and any hint about ordering or result size, which is minor for a read-only listing tool.

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 description coverage is 0%, so the description carries the burden. It meaningfully explains conversation_id (scoping to one conversation's calls) and implicitly the tool_name and failed_only filters via 'which tool' and 'whether it failed'. The limit parameter is never mentioned, and no defaults, ranges, or filter combination behavior are clarified.

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

Purpose5/5

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

States a specific verb and resource ('Read the calls the bot made to the store's own tools') and enumerates what each record contains (tool, arguments, failure status). The parenthetical examples (room availability, order status, checkout) pin the scope tightly and make it distinguishable from get_conversation or list_conversations.

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?

One concrete usage path is given: 'Use conversation_id to see every call behind one conversation.' There is no guidance on when to prefer this over siblings like get_conversation, and no statement about when not to use it or how tool_name/failed_only narrowing should be chosen.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.