Skip to main content
Glama

bx_dictionary_format

Read-onlyIdempotent

Retrieve custom L2/L3 JSON Schema, format requirements, and complete Chinese or English examples without files or a model.

Instructions

读取自定义L2/L3的格式规范、JSON Schema与完整中英文示例。 / Get the custom L2/L3 JSON Schema, format requirements and a complete Chinese or English example. No files or model required.

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

Input Schema

NameRequiredDescriptionDefault
layerNo
languageNo

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

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: no files or model are needed, and the payload is a schema plus format requirements plus a complete worked example. That pre-call expectation of cost and content is valuable.

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 front-loaded sentences: the resource and its contents first, then the no-prerequisites note. The bilingual restatement doubles the length without adding information for an agent, but given the likely mixed-language audience it is defensible rather than wasteful, so this is only a small deduction.

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 explained, and the two parameters are enums. What is missing is default behavior when layer or language is omitted. For a simple, read-only reference tool this definition is nearly complete.

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 description must compensate; it partially does by pairing 'L2/L3' with the layer parameter and 'Chinese or English' with the language parameter. Both parameters are enums and self-explanatory. However, it never states the defaults or behavior when either optional parameter is omitted, leaving a real gap.

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 and resource: it 'gets' the custom L2/L3 JSON Schema, format requirements, and a complete zh/en example. An agent can tell this is the reference/spec-reading tool rather than the validate or import siblings. It stops short of naming a sibling, 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 files or model required' implies this is a cheap, prerequisite-free way to fetch the spec, which hints at when to call it. However, there is no explicit when/when-not guidance or reference to alternatives such as bx_dictionary_validate for checking an existing document. Usage must be inferred.

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