Skip to main content
Glama

Harvest progress

inspo_status

Check progress of design-reference harvest jobs, including per-section counts, crawled sites, phase, and recent log; set cancel to stop a running job.

Instructions

Progress of harvest jobs: references per section vs target, sites crawled, phase, recent log. Pass cancel:true to stop the running job.

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

Input Schema

NameRequiredDescriptionDefault
cancelNo
sessionNoSession id. Defaults to the most recent session in this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that cancel:true terminates the running job — a destructive side effect an agent must know — but does not say whether cancellation is reversible, what happens to partial results, or whether the call is otherwise read-only.

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?

Two tight sentences with the returned fields front-loaded and the mutating option last. Nothing is wasted, though the field list is a comma run rather than structured.

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 status tool with no output schema and no annotations, listing the reported fields and the cancel behavior covers most of what an agent needs. Gaps remain around post-cancel state, error behavior when no job exists, and the session default.

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%: session is documented in the schema, while cancel is not. The description compensates by explaining exactly what cancel:true does, which is the meaning an agent needs; only the session-default behavior is left entirely to the schema.

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 gives a concrete resource (harvest job progress) and enumerates the reported fields — references per section vs target, sites crawled, phase, recent log — so the agent knows exactly what comes back. It is clear, though it never contrasts itself with the sibling inspo_harvest that presumably starts such a job.

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?

Usage is only implied: poll this while a harvest is running, and pass cancel:true to stop it. There is no explicit statement of when to call it versus inspo_harvest or inspo_next_round, and no note that a session must exist first.

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