census_list_syncsList syncs (a sync maps a source model to a destination object and keeps them in sync). Returns id, label, status, source_attributes, destination_attributes. Census: GET /syncs.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) for pagination. | |
| per_page | No | Number of records per page. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. The description adds the HTTP method (GET) and the returned fields, but does not disclose additional behavioral traits such as pagination behavior, rate limits, or any side effects. It is consistent with annotations but adds minimal value beyond them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the core purpose, and includes a concise explanation of a sync and the return fields. Every sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description specifies the returned fields (id, label, status, source_attributes, destination_attributes). The parameter schema covers pagination fully. For a simple list tool, the description is complete and sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with both parameters (page and per_page) described in the schema. The description does not add any additional meaning or examples beyond what the schema already provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists syncs, explains what a sync is, and specifies the returned fields (id, label, status, source_attributes, destination_attributes). This distinguishes it from sibling tools like census_get_sync (single sync) and census_trigger_sync (trigger).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for listing all syncs and mentions returned data, but does not explicitly state when to use this tool versus alternatives like census_get_sync for a single sync or census_trigger_sync for triggering. No exclusions or when-not guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource type (destination, model, source, sync, sync run, segment, workspace) with clear get/list/trigger actions. No overlapping purposes; agents can easily distinguish which tool to use for a given operation.
All tools follow a consistent 'census_verb_noun' pattern (e.g., census_get_destination, census_list_syncs). The only action tool, census_trigger_sync, also fits the pattern. No mixing of casing or verb styles.
13 tools is appropriate for a data integration platform that manages multiple resource types (destinations, sources, models, syncs, etc.). It's slightly on the higher side but well-scoped for the domain.
The set covers get, list, and trigger operations, but lacks create, update, and delete for resources. While Census API may not expose mutating operations via MCP, the surface is incomplete for full lifecycle management.