Skip to main content
Glama

bx_dictionary_lookup

Read-onlyIdempotent

Look up paginated lexical entries in explicitly digest-bound dictionaries to retrieve domain terms without semantic interpretation or authorization.

Instructions

在已绑定字典中分页查询词条,不作语义裁决。 / Look up lexical entries only in the explicitly digest-bound dictionaries. Not semantic interpretation or authorization.

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": {
      "dictionaries": "<dictionaries>",
      "query": "<query>"
    },
    "name": "bx_dictionary_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
offsetNo
pack_idNo
dictionariesYes

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

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, and the description adds genuine value on top: results are paginated, restricted to bound dictionaries, and explicitly are not a semantic verdict or authorization. It does not describe pagination termination, ordering, or what a miss looks like, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences (bilingual) with zero filler; the core scope constraint is front-loaded and the exclusion clause follows immediately. Nothing could be dropped without losing content.

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 and annotations cover the safety profile, so return values and side effects need no explanation. However, a four-parameter tool with a nested sha256/selection object at 0% schema coverage still leaves the agent guessing at the most consequential inputs, which the description does not address.

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

Parameters2/5

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

Schema description coverage is 0% across 4 parameters, including an opaque nested object with sha256 and a selection.{l2,l3} sub-structure, plus pack_id and offset; the description explains none of them. Only 'paged' loosely hints at offset, leaving the most complex required parameter (dictionaries) entirely undefined, so the description fails to compensate for the coverage 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?

Names a concrete verb+resource (paged lexical entry lookup) and constrains scope to 'explicitly digest-bound dictionaries', which separates it from generic text analysis tools. It also states a negative scope ('not semantic interpretation or authorization'), though it never names a specific sibling tool such as bx_analysis_submit for the semantic path.

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?

The phrase 'only in the explicitly digest-bound dictionaries' implies a prerequisite (dictionaries must be bound first) and rules out semantic adjudication usage, but gives no explicit when-to-use/when-not or routing to an alternative. An agent must infer that binding happens elsewhere and that interpretation work belongs to another tool.

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