Skip to main content
Glama

ai_modeling_project_history

Read-only

Lists a project's saved operation history so you can review past modeling actions and track changes by project ID.

Instructions

List a project’s saved operation history.

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": {
      "project_id": "<project_id>"
    },
    "name": "ai_modeling_project_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.8/5.0
Behavior2/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 safety is covered. The description adds only that the history is 'saved' (persisted), and says nothing about ordering, pagination, retention window, or whether all operation types are included — the details that distinguish one history endpoint from another.

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 sentence, zero padding, and the resource is stated immediately. It is efficient, though the terseness borders on under-specification rather than crispness.

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 one-parameter read tool with no output schema, the barrier is low, and annotations cover the safety profile. Still, the description omits what a history entry conceptually contains and how this differs from the closely named history siblings, which is the main thing an agent needs before calling.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter project_id, so the description must carry the meaning. The possessive 'a project's' only weakly implies project_id scopes the history, and the description never explains the accepted identifier format (the schema's pattern/minLength constraints go unmentioned) or what happens for an unknown project.

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 pairs a specific verb ('List') with a specific resource ('a project's saved operation history'), which tells an agent exactly what it returns. It offers no differentiation from near-name siblings such as ai_modeling_history or ai_modeling_project_history_check, so the agent cannot tell which of those to pick.

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 named alternative. The only signal is the phrase 'saved operation history', leaving the agent to infer that this is a read-only audit/log lookup and that other history tools serve different purposes.

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