Skip to main content
Glama

bx_dictionaries_list

Read-onlyIdempotent

Lists L2/L3 dictionary IDs, versions, digests, and test-only flags to help identify available domain libraries and verify their status; no active L1 is included.

Instructions

列出L2/L3字典、版本、摘要和测试标记。 / Discover B-335 L2/L3 IDs, versions, digests and test-only flags. No active L1.

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_dictionaries_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's contribution is the scoping disclosure "No active L1" — a genuine behavioral constraint not expressed in the annotations. It does not discuss ordering, caching or volume, but with annotations and an output schema present, that omission is minor.

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?

Very short and front-loaded: the resource and returned fields come first, the scope caveat last. The bilingual duplication doubles the token count for the same content, which is the only waste, though it is plausibly intentional for an internationalized catalog.

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 zero-parameter, read-only listing tool with full annotations and an output schema, the description says enough: what is enumerated and what is excluded. An agent knows when it is applicable and what to expect. The only gap is the absence of a pointer for the L1 case.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals a call with no filters or arguments, consistent with 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?

States a specific verb (list/discover) and resource (L2/L3 dictionaries) and enumerates the returned fields: IDs, versions, digests and test-only flags. It also declares a scope boundary ("No active L1"), which separates it from the lookup/bind siblings. It stops short of naming which sibling to use for L1 data, so it is clear but not fully differentiated.

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?

"No active L1" implies the tool is not the right choice when active L1 dictionaries are needed, which is useful implicit guidance. However, no alternative is named (e.g. bx_dictionary_lookup or bx_dictionary_format) and there is no statement of prerequisites or when this should precede bx_dictionaries_bind. Usage is implied rather than stated.

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