Skip to main content
Glama

ai_modeling_refine_history

Read-only

Retrieve and review human refinement service requests without placing an order, so you can inspect past requests before deciding next steps.

Instructions

Read your human refinement service requests; does not place an order.

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

Input Schema

NameRequiredDescriptionDefault
page_numNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description reinforces this by denying order placement, but adds nothing about pagination behavior, default window, or what a returned record looks like. With annotations carrying the safety burden, this is an adequate but thin contribution.

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?

A single short clause pair, front-loaded with the verb and resource, with the limitation stated immediately after. Nothing is wasted and nothing important is buried.

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 tool with no output schema, the definition covers the essential scope and non-mutation guarantee. It is incomplete in that nothing describes the shape or volume of returned history entries, which the absent output schema leaves entirely unaddressed.

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 both page_num and page_size, so the description is the only place meaning could be supplied — yet it says nothing about paging. The schema gives types, defaults, and bounds, but the agent gets no guidance on how page size affects results or how to iterate.

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 ("Read") and resource ("human refinement service requests"), which is enough to distinguish it from an action tool like ai_modeling_refine_submit. It stops short of saying what a refinement request record actually contains, so the resource remains slightly abstract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause "does not place an order" gives a clear when-not signal and implicitly routes ordering to a sibling submit tool. There is no positive framing of when to reach for this reader (e.g., to review prior requests before submitting), so the guidance is useful but one-sided.

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