Skip to main content
Glama
Sign In
afya-mcp

afya-mcp

by gabrielmahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

nhif_coverage_query

Look up NHIF/SHA coverage for a specific procedure or condition. Provide a query and optional member tier to get coverage information.

Instructions

Query NHIF/SHA coverage for a procedure or condition. DEMO.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
member_tierNostandard

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/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 adds 'DEMO' to indicate a demonstration version. It fails to disclose important behavioral traits like read-only nature, data freshness, or limitations of the demo environment.

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?

The description is brief (two sentences) and front-loaded with the core functionality. However, the 'DEMO' tag could be integrated into the first sentence, and important details are omitted, so it is not maximally efficient.

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

Completeness2/5

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

Despite having an output schema, the description gives no hint about the response format or key fields. With 2 parameters lacking guidance and a set of sibling tools without differentiation, the description is incomplete for an AI agent to use effectively.

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

Parameters1/5

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

The input schema has 0% description coverage, and the description adds no meaning for parameters: 'query' (what format?) and 'member_tier' (what are valid values?). The description does not compensate for the missing schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Query' and the resource 'NHIF/SHA coverage' for a procedure or condition, distinguishing it from sibling tools like health_facility_finder or essential_medicines.

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 description implies usage for checking coverage but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusion criteria.

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

Deploy Server

Other Tools