bahmni-mcp

getAddressHierarchyEntry

Retrieve a specific address hierarchy entry by its UUID. Access geographic hierarchy details from a Bahmni instance.

Instructions

Get address hierarchy entry

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": {
      "uuid": "<uuid>"
    },
    "name": "getAddressHierarchyEntry"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, and the description only implies a read operation via the verb 'get'. It does not disclose read-only behavior, error conditions, authentication needs, or any other behavioral traits. The description carries the full burden but fails to provide sufficient transparency.

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

Conciseness2/5

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

The description is extremely concise but under-specified. It is a single sentence that does not front-load key details or earn its place by adding value beyond the name. It sacrifices completeness for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the input (one parameter) and lack of annotations or output schema, the description is completely inadequate. It does not explain the purpose, usage, or expected outcome, making it nearly impossible for an agent to use correctly.

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?

The schema has one parameter 'uuid' with 0% description coverage, and the tool description does not explain what UUID to use (e.g., which entity's UUID, how to obtain it). The description adds no meaning beyond 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?

The description clearly identifies the action (get) and resource (address hierarchy entry). However, it does not differentiate from other sibling get tools like getPatientById or getDrugById, which may confuse an agent selecting among similar verbs.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusion criteria, leaving the agent to rely solely on the tool name.

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