Third Hemisphere AI Authority Index

Record progress on a Blueprint item

update_blueprint_progress

Idempotent

Record where a play or move stands: not_started, in_progress, done, skipped, with an optional note of what was done. DIY Blueprint tool: needs a key whose plan includes them (https://thirdhemisphere.agency/ai-authority-index/data#blueprint-diy).

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": {
      "item_id": "<item_id>",
      "status": "<status>"
    },
    "name": "update_blueprint_progress"
  }
}

Input Schema

Name	Required	Description
`note`	No
`status`	Yes
`item_id`	Yes
`blueprint_id`	No	From list_my_blueprints. Optional when the address has one Blueprint.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover idempotency, non-destructiveness, and the write nature of the call. The description adds a meaningful auth prerequisite, but does not explain whether this creates or overwrites an item, how blueprint_id resolves, or what side effects occur beyond the status update.

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?

The description is two efficiently structured sentences. The action and statuses are front-loaded, and the auth note follows without wasted words, though the parenthetical URL slightly interrupts flow.

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 non-destructive, idempotent mutation with no output schema and incomplete parameter documentation, the description is adequate but not fully complete. It covers statuses and auth requirements yet leaves item_id semantics and the exact update behavior underspecified.

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 coverage is only 25%, so the description carries a heavy burden. It clarifies status values and that note is optional context, but it leaves item_id completely unexplained and adds no detail on how blueprint_id is resolved beyond what the schema already says.

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 uses a specific verb ('Record') and resource ('where a play or move stands') and enumerates the four statuses, making the write operation clear. It implicitly distinguishes from the read-only sibling get_blueprint_progress, though it does not name that sibling explicitly.

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?

The description gives an important prerequisite ('needs a key whose plan includes them'), which helps determine eligibility. However, it does not state when to use this versus reading progress with get_blueprint_progress or what to do when the item does not yet exist.

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

All Third Hemisphere AI Authority Index tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?