Skip to main content
Glama

dhis2_metadata

Query DHIS2 metadata resources using filters and field selection. Retrieve specific items like data elements, indicators, or organisation units with a single call.

Instructions

Query DHIS2 metadata with a simplified interface.

Convenience wrapper around dhis2_query() for common metadata lookups.

Args:
    resource: Metadata resource type — e.g. "dataElements", "indicators",
              "organisationUnits", "programs", "dataSets", "trackedEntityTypes".
    filters:  Filter expressions in DHIS2 format, e.g. ["name:ilike:malaria", "valueType:eq:NUMBER"].
    fields:   Comma-separated field list (default: "id,name,shortName").
    paging:   Set True to get only the first page (faster for large resources).

Examples:
    dhis2_metadata("dataElements", ["name:ilike:HAT", "valueType:eq:INTEGER"])
    dhis2_metadata("programs", fields="id,name,programType,trackedEntityType[id,name]")
    dhis2_metadata("organisationUnits", ["level:eq:3"], fields="id,name,level,parent[id,name]")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYes
filtersNo
fieldsNoid,name,shortName
pagingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions that setting paging to True returns only the first page and is faster, which adds behavioral context. However, it does not explicitly state that the tool is read-only, describe the return format, or disclose potential side effects or authentication needs.

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 well-structured with sections for Args and Examples, making it easy to parse. While it is somewhat lengthy, every sentence adds value, and the use of code examples enhances clarity. A slight reduction in verbosity could earn a 5.

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?

Given that an output schema exists, the description does not need to detail the return format explicitly, but it provides examples that imply the structure. It covers the key aspects: purpose, parameters, and usage context. However, it lacks information on error handling or rate limits, which would make it more complete.

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

Parameters5/5

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

The schema has 0% description coverage, but the description's 'Args' section adds significant meaning: it explains what 'resource' expects (e.g., 'dataElements'), the format of 'filters' with examples, the default for 'fields', and the behavior of 'paging'. This fully compensates for the missing schema descriptions.

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 it is a 'Convenience wrapper around dhis2_query() for common metadata lookups', specifying the verb (query) and resource (DHIS2 metadata). It also distinguishes from its sibling tool 'dhis2_query' by being a simpler interface, fulfilling the purpose clarity criterion.

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

Usage Guidelines4/5

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

The description provides examples and indicates it is for 'common metadata lookups' as a simpler alternative to dhis2_query. However, it does not explicitly state when not to use it or list alternative tools beyond mentioning dhis2_query. This is clear but lacks explicit exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server