Skip to main content
Glama

ai_modeling_history

Read-only

Lists recent modeling tasks created by this CLI, showing task IDs, names, statuses, and output directories so agents can inspect prior runs.

Instructions

List recent tasks created by this CLI (task ids, names, statuses, output dirs).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds real value by disclosing the returned fields (ids, names, statuses, output dirs) in the absence of an output schema, but says nothing about ordering, recency window, or whether "recent" is bounded.

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?

One front-loaded sentence with a compact parenthetical listing return fields; no wasted words. It is arguably too terse for the routing decision it needs to support, but nothing is padded.

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 read-only single-param lister, the description covers purpose, scope, and return contents, and annotations handle safety. The main gap is differentiation from the other *_history siblings and any hint about the cap on results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage and the description never mentions it. It says nothing about how many tasks are returned, the default of 10, the 100 cap, or whether the limit applies before or after filtering.

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?

Specific verb+resource: "List recent tasks created by this CLI" and it even enumerates the fields returned (task ids, names, statuses, output dirs). The "created by this CLI" scope hints at why it differs from project-level history siblings, but those siblings (ai_modeling_project_history, ai_modeling_refine_history) are never named, so the agent must still infer the distinction.

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?

No explicit when-to-use statement and no named alternatives, despite several close siblings in the history family. The phrase "recent tasks created by this CLI" implies a local/CLI scope, which is the only routing signal the agent gets.

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

Deploy Server

Other Tools