Skip to main content
Glama
Sign In
SurveyBridge AI

SurveyBridge AI

by onovo007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

surveybridge_get_indicator_series

Retrieve indicator time-series aggregates for selected countries, optionally adding them to a persistent project snapshot for later export.

Instructions

Retrieve aggregates and create a persistent project_id. Optional project_id adds an indicator to a new snapshot. Up to 500 rows returned; export contains all rows.

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

Input Schema

NameRequiredDescriptionDefault
to_yearNo
breakdownNonational
from_yearNo
project_idNo
country_idsYes
indicator_idYes

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
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that up to 500 rows are returned, that export contains all rows, and that project_id creates a persistent project_id / adds an indicator to a snapshot, but it does not explain pagination, permissions, or the precise mutation semantics of project_id.

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 short and front-loads the retrieval action and row limit. However, the second sentence about project_id is confusingly repetitive and could be integrated more clearly with the first.

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?

This is a relatively complex tool with six parameters and no annotations, and the description covers only row limits and an ambiguous project_id side effect. Even though an output schema exists, the description omits parameter meanings and usage context needed to invoke the tool correctly.

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 the description must compensate for six undocumented parameters. It adds meaning only for project_id and does not explain indicator_id, country_ids, from_year, to_year, or the breakdown default of 'national'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it retrieves aggregates, but does not specify that it retrieves indicator series data for given countries, years, or breakdowns. It also introduces a side effect about creating a persistent project_id, which makes the core purpose less clear rather than distinguishing it from siblings such as surveybridge_search_indicators or surveybridge_export_project.

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 use this tool versus siblings like surveybridge_search_indicators or surveybridge_export_project. The mention of optional project_id implies a snapshot-related mode, but it does not explain when an agent should supply project_id or choose this tool over alternatives.

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