Skip to main content
Glama

get_conversion_history

Retrieves the history of all conversions performed in this session, with optional status and limit filters.

Instructions

Get the history of all conversions performed in this session

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of records to return (default 20)
statusNoFilter by status (default 'all')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and mostly fails it. 'Get' and 'history' imply a read, but nothing states whether results are ordered, whether the history is retained beyond the session, what a record contains, or how errors are represented.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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?

The tool is simple with two optional parameters, so the description covers the core purpose. However, with no output schema and no annotations, it leaves the return shape, ordering, and pagination behavior entirely unspecified.

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 100%, with both limit and status fully documented including defaults and the enum values. The description adds nothing about them, so the baseline 3 applies; the schema does all the work here.

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?

States a specific verb and resource: retrieving the history of conversions performed in the current session. That scope makes it clearly distinct from the convert_* siblings, which perform conversions rather than report on them. It stops short of naming any sibling or stating what the records contain.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The phrase 'in this session' implicitly bounds the scope, but the agent must infer that this is a retrospective lookup tool rather than part of a conversion workflow.

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