Skip to main content
Glama

bx_capabilities

Read-onlyIdempotent

Discover the pinned runtime, contracts, and bilingual built-in help by selecting a language and help topic; optionally query one tool by name. Use it to find usage guidance without a model call.

Instructions

查看版本、合同及中英帮助;language选zh-CN或en,help_topic选overview/tools/examples/troubleshooting;工具主题可用tool_name查询单个工具。 / Discover the pinned runtime, contracts and bilingual built-in help. Use language zh-CN or en and help_topic overview, tools, examples or troubleshooting; optional tool_name selects one tool in the tools topic. No model call.

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

Input Schema

NameRequiredDescriptionDefault
languageNo
tool_nameNo
help_topicNo

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the runtime version is 'pinned' (stable, reproducible answers) and 'No model call' means no inference cost, latency, or model invocation. It does not discuss caching or output shape, but the output schema covers the latter.

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 content is front-loaded, starting with what is discoverable and then the parameter choices, and both language halves are parallel so an agent can read either. The duplication of enum values in both Chinese and English is somewhat redundant with the schema, but the bilingual form is justified by the tool's own bilingual purpose, and there is no filler.

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?

For a three-optional-parameter read-only help tool with an output schema, this is close to sufficient: it tells what topics exist, how to narrow to one tool, and that no model is invoked. The only meaningful gap is what happens when language or help_topic is omitted (defaults), which neither the schema nor the description states.

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 description coverage is 0%, so the description carries the full burden, and it does cover all three parameters. The most valuable addition is the dependency: tool_name only makes sense together with the 'tools' help_topic. The language and help_topic explanations largely restate the enum values already in the schema, and no default behavior is stated when parameters are omitted.

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 names a specific verb and a concrete set of resources: pinned runtime version, contracts, and bilingual built-in help, with optional per-tool lookup. An agent can immediately tell this is the meta/help tool rather than an analysis or dictionary sibling. It stops short of an explicit sibling contrast, but the resource set is distinctive enough for disambiguation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete routing guidance: pick language zh-CN or en, and pick help_topic from overview/tools/examples/troubleshooting, with tool_name selecting a single tool within the tools topic. That conditional pairing is real usage guidance beyond the schema. No when-not-to-use or alternative-tool exclusions are stated.

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