Skip to main content
Glama

bx_result_recheck

Idempotent

Recompute saved submitted calculations using the same core to create a new revision without new model requests, preserving original results.

Instructions

复算保存的原候选,生成新版本,零次新模型调用。 / Recompute saved submitted calculations using the same B-335 Core. Preserve the original LLM proposal and old results; create a new revision with zero model requests.

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>",
      "revision": "<revision>",
      "request_id": "<request_id>"
    },
    "name": "bx_result_recheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
project_idYes
request_idYes

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower, and the description still adds real context: the original LLM proposal and old results are preserved rather than overwritten, and the operation costs no model calls. That preservation and cost guarantee is exactly the kind of thing an agent cannot derive from the annotations.

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 per language, with the action and the preservation guarantee front-loaded. The bilingual duplication is redundant for a single-language reader but is a deliberate localization choice rather than padding.

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?

An output schema covers the return shape and the annotations cover the safety profile, so the biggest remaining gaps are behavioral preconditions and parameter meaning. For a mutating recompute that produces a new revision, the description should say what state the source result must be in and how revision is used.

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 three required parameters, so the description carries the full burden and does not meet it. It never explains what 'revision' selects (source revision to recompute? target revision to write?), what role 'request_id' plays (idempotency key?), or any format expectations, leaving all three undocumented in both places.

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 ('recompute') on a specific resource ('saved submitted calculations') and states the outcome ('create a new revision'), which separates it from a plain retrieval like bx_result_get or a fresh submission like bx_analysis_submit. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 'zero model requests' and 'same B-335 Core' phrasing implies the situation to pick this over resubmitting, but the description never states a when-to-use condition, prerequisites (must the original be in submitted state?), or exclusions. Usage is left to inference from the phrasing.

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