Skip to main content
Glama

list_ai_run_history

Read-only

Past AI-coach runs (plans generated, check-in replies, adjustments) for your clients, newest first, with status, rationale and created artifacts. Pass clientId to narrow to one client.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
clientIdNoClient's User _id (from list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description usefully adds result ordering and the fields each record carries (status, rationale, artifacts), but says nothing about how the 'limit' parameter affects paging or about result size, which is the main behavioral unknown left for a list tool.

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 tight sentence that front-loads the resource and tacks the filter hint on at the end. Nothing is wasted, though the phrasing is dense and could be split for scannability.

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?

For a simple two-parameter, read-only, no-output-schema list tool, the description covers what is returned and the default ordering. It omits the limit/pagination behavior and any sense of typical volume, which is the remaining gap an agent would want filled.

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?

Schema coverage is 50%: clientId is documented in the schema, while limit only has default/min/max and no prose. The description adds that clientId acts as a narrowing filter, which is meaningful, but it does not explain the limit parameter's effect, so it only partly 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?

States a specific resource ('Past AI-coach runs') plus what the records contain ('plans generated, check-in replies, adjustments') and the ordering ('newest first'). An agent can distinguish this from review-oriented siblings, though it never names them 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?

Only guidance given is the optional filter hint ('Pass clientId to narrow to one client'). There is no statement of when to prefer this over nearby tools such as get_client_ai_history or list_ai_runs_awaiting_review, so the agent must infer which history surface to use.

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.