Skip to main content
Glama

Metis · DHIS2 Expert — DHIS2 Metadata

dhis2_metadata

Retrieve DHIS2 metadata by resource type with optional filters and field selection. Query data elements, indicators, organisation units, and more using DHIS2 filter syntax.

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
fieldsNoid,name,shortName
pagingNo
filtersNo
resourceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full behavioral transparency burden. It explains the paging parameter behavior ('get only the first page (faster for large resources)') and provides examples showing typical usage. It does not contradict any annotations (none present). However, it could explicitly state idempotency or read-only nature.

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 (Args, Examples) and uses bullet points for parameter descriptions. It is concise yet informative, though the examples could be slightly trimmed without loss of clarity.

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

Completeness5/5

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

Given 4 parameters (1 required), no enums, and an existing output schema, the description is complete. It covers all parameters, provides usage examples, and references the sibling tool dhis2_query. No gaps are left for an agent to misinterpret.

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 description coverage is 0%, so the description must add meaning. It does so by explaining each parameter: resource (with examples), filters (format with example), fields (default value), and paging (behavior). This goes beyond the raw schema, though it could provide more exhaustive resource examples or filter syntax details.

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 'Query DHIS2 metadata with a simplified interface' and identifies itself as a 'Convenience wrapper around dhis2_query()', using specific verbs and resource types. It distinguishes itself from its sibling tool dhis2_query by emphasizing simplicity.

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 this is for common metadata lookups (as a wrapper) but does not explicitly state when to use this tool versus dhis2_query or other alternatives. It lacks explicit when-to-use or when-not-to-use guidance, leaving the agent to infer from 'simplified interface'.

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