Skip to main content
Glama
Sign In
SurveyBridge AI

SurveyBridge AI

by onovo007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

surveybridge_search_indicators

Search official indicator metadata locally to retrieve exact IDs, definitions, and denominators for DHS survey indicators.

Instructions

Search official indicator metadata locally; return exact IDs, definitions and denominators.

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": "surveybridge_search_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
dataNo
sourceNo
statusNook
warningsNo
truncatedNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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. 'Locally' usefully signals no remote/authenticated access, but the description says nothing about whether matching is fuzzy or exact, how limit affects results, or pagination — important given that search results drive indicator selection.

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?

A single front-loaded sentence with no waste. Brevity is appropriate, though at two params of zero coverage it undersells rather than over-explains.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and no annotation disclosure is expected for a local read. Still, with zero parameter documentation and no guidance on matching behavior, the definition leaves the agent guessing on core call semantics.

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?

Schema description coverage is 0% across both parameters. The description never explains what 'query' matches against (name, definition, denominator) or what 'limit' (default 20) truncates, leaving both parameters fully undocumented.

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?

States a specific verb (Search) and resource (official indicator metadata), scoped to 'locally', and names the outputs: IDs、definitions、denominators. That distinguishes it from siblings like surveybridge_get_indicator_series, which fetches series data rather than metadata, though the distinction is only implicit.

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?

'Locally' hints that this is the metadata-lookup path and that series retrieval lives elsewhere, but it never names the alternative tool or states when not to use it. The agent must infer the routing.

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