Skip to main content
Glama

bx_result_get

Read-onlyIdempotent

Retrieve the joint LLM/Core summary, calculations, differences, and immutable report references for an exact project revision without rerunning or translating results.

Instructions

读取指定结果版本的LLM、计算器、差异和报告。 / Read the joint LLM/Core summary and immutable result/report references for an exact revision. No rerun or translation.

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>"
    },
    "name": "bx_result_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
project_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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the returned references are 'immutable' and that no rerun or translation occurs, which is genuinely useful cost/side-effect context beyond the annotations. It stops short of describing pagination, size, or what happens when the requested revision does not exist.

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 short sentences, verb-first and front-loaded, with the key constraint ('No rerun or translation') placed at the end as a qualifier. The bilingual duplication is redundant for a single-locale agent 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, and the description still characterizes the payload (summary plus immutable result/report references). For a two-parameter read tool with full annotations, this is close to sufficient; the main residual gap is failure behavior for a nonexistent revision.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the two parameters (project_id UUID pattern, revision integer >= 0) rely entirely on the description, which only says 'specified result version' and 'exact revision'. That clarifies that revision selects a version rather than a count, but adds no format, ordering, or error semantics for either parameter. Partial compensation only.

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 specific verb ('Read') and resource ('joint LLM/Core summary and immutable result/report references') scoped to 'an exact revision'. The clause 'No rerun or translation' implicitly separates it from the recompute path (bx_result_recheck), though it never names that sibling. Terminology like 'LLM/Core' and 'result version' is domain jargon that leaves the exact payload slightly fuzzy.

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: 'for an exact revision' plus 'No rerun' suggests this is the retrieval path once a revision exists, and that recomputation belongs elsewhere. There is no explicit when-to-use/when-not-to-use statement and no named alternative, so the agent must infer the routing from the negative constraint.

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