Skip to main content
Glama

dhis2_metadata

Retrieve DHIS2 metadata for resources like data elements, indicators, and programs. Apply filters and select fields to get only the information needed.

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?

With no annotations, the description must convey all behavioral traits. It explains the paging parameter behavior (default returns all pages, setting True returns only first page). However, it does not explicitly state that the tool is read-only, nor does it discuss side effects, authentication needs, or rate limits. The examples help but leave gaps.

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?

The description is concise: a two-line purpose, a bulleted Args section, and three usage examples. Every sentence adds value, and the structure efficiently conveys all necessary information without redundancy.

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 the tool's moderate complexity (4 params, 1 required, no enums) and the presence of an output schema, the description covers the key aspects: purpose, parameters, and usage examples. It does not detail the return format, but the output schema covers that. It could benefit from mentioning that the tool is a query (read-only), but overall it is sufficient.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It provides clear explanations for all four parameters: resource (with examples), filters (with format and example), fields (with default and nested field example), and paging (with behavior description). This adds significant meaning beyond the bare schema.

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 tool queries DHIS2 metadata, specifies it is a simplified interface and a wrapper around dhis2_query(), and differentiates from that sibling tool by implying it is for common lookups. Examples further clarify the resource types.

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 positions the tool as a 'convenience wrapper' for common metadata lookups, implying use when a simpler interface is desired over dhis2_query(). It does not explicitly say when not to use it, but the sibling tool name is mentioned, providing context.

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_PH'

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