Skip to main content
Glama

Show recent pulls

history
Read-only

View recent pulls newest first and get each pull ID needed to rerun a previous pull.

Instructions

Show the user's last pulls, newest first (for 'show my last pulls'). Each has an id that rerun takes.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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=false, so the safety profile is covered. The description adds useful behavior beyond that: result ordering (newest first) and the fact that each entry carries an id consumable by rerun. It says nothing about how many results come back or what happens at the default limit.

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?

Two short sentences, front-loaded with the core action and ordering, followed by the rerun handoff. No filler or redundancy.

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 read-only list tool with annotations covering safety and no output schema, the description covers purpose, ordering, and the id handoff. The notable gap is the undocumented limit parameter, which is the only thing an agent must decide when invoking it.

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?

There is one parameter (limit, default 10) with 0% schema description coverage, and the description never mentions it. An agent cannot learn from the description what limit controls or its default, so the single parameter is effectively undocumented.

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 ('Show the user's last pulls') plus an ordering guarantee ('newest first'), which is more than the title alone conveys. It also distinguishes itself from the rerun sibling by noting the id handoff, though it does not contrast with saved_pulls.

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?

Provides a trigger phrase ('for show my last pulls') and a clear downstream handoff to rerun via the returned id. It gives no when-not guidance and does not say how this differs from saved_pulls, so usage is implied rather than fully scoped.

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