Skip to main content
Glama
SurveyBridge AI

SurveyBridge AI

by onovo007

surveybridge_list_surveys

Lists completed survey rounds, types, and fieldwork dates for specified countries and optional year range so users can check which datasets are available before analysis.

Instructions

List completed survey rounds, types and fieldwork dates; data availability varies.

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": {
      "country_ids": "<country_ids>"
    },
    "name": "surveybridge_list_surveys"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_yearNo
from_yearNo
country_idsYes

Output Schema

NameRequiredDescriptionDefault
dataNo
sourceNo
statusNook
warningsNo
truncatedNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden. 'Data availability varies' is the only behavioral hint — it does not explain permissions, pagination, whether unfiltered calls are allowed, or how missing rounds are represented, which is significant for a listing tool with zero annotation coverage.

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 compact sentence with the resource and returned fields front-loaded and no filler. Its brevity is efficient rather than padded, though it leans toward under-specification given the undocumented parameters.

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?

An output schema exists, so return values need not be explained. However, for a 3-parameter tool with 0% schema description coverage, no annotations, and no usage guidance, the description leaves too much for the agent to infer about country scope and year filtering.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters (country_ids, from_year, to_year) are undocumented structurally. The description mentions no parameter semantics at all — not that country_ids is required, nor that from/to_year bound fieldwork dates — so it fails to compensate for the coverage gap.

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 (List) and a specific resource (completed survey rounds, types, fieldwork dates), so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from siblings such as surveybridge_list_countries, though the resource noun is distinct enough to disambiguate.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives (e.g. surveybridge_list_countries or surveybridge_search_indicators). The phrase 'data availability varies' hints at a caveat but provides no selection criteria or preconditions.

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