Skip to main content
Glama

bx_dictionaries_bind

Read-onlyIdempotent

Validates and binds an explicit L2/L3 dictionary selection, returning its immutable digest for fixed domain context without task authority.

Instructions

绑定显式字典选择,取得固定摘要。 / Validate an explicit L2/L3 selection and return its immutable digest. No task authority.

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": {
      "selection": "<selection>"
    },
    "name": "bx_dictionaries_bind"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectionYes

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.6/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 still adds two things the annotations do not: the returned digest is immutable, and the call carries no task authority, meaning no task-scoped state is bound as a side effect. That is genuine added context, though the auth or precondition requirements remain unstated.

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 with the key constraint ('explicit', 'immutable digest', 'no task authority') front-loaded. The Chinese and English lines restate each other, which costs space but is defensible for a bilingual tool surface; no sentence is filler.

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 exists, so return values need not be explained. However, the tool's real ambiguity is left open: the name says 'bind' while the description says 'validate', and the nested selection semantics are undocumented. For a tool whose only input is a nested object, that leaves an agent guessing at correct invocation.

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% for a single nested object with l2 and l3, so the description must compensate. Naming 'L2/L3 selection' ties the description to the two nested fields, which helps, but it never explains what L2 and L3 denote, whether null is meaningful, or what happens when both are null or empty.

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 English line gives a specific verb and resource: validate an explicit L2/L3 selection and return its immutable digest. That is far more informative than the bare name 'bx_dictionaries_bind', which suggests binding rather than validation. It stops short of naming how it differs from the sibling bx_dictionary_validate, so an agent must guess which of the two to call.

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?

'Explicit' selection plus 'No task authority' implies this tool is for caller-supplied L2/L3 pairs and not for resolving a selection from a task context. That is a real boundary hint, but it is phrased obliquely and never states when to prefer this over bx_dictionary_validate or bx_dictionary_lookup. Usage is implied rather than prescribed.

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