census_list_sourcesList configured data warehouse sources (Snowflake, BigQuery, Redshift, Databricks, etc.). Census: GET /sources.
| 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 underlying API endpoint but does not disclose behavioral traits like pagination behavior, result format, or whether the list is comprehensive. This provides minimal added value beyond annotations.
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?
A single sentence that front-loads the core purpose. No extraneous words. However, it could be slightly more structured by mentioning pagination or return type.
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?
For a simple list operation with no output schema, the description covers the basic purpose but omits return value details (e.g., paginated list of source objects). Given the annotations and schema, it is adequate but not fully complete.
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 description coverage is 100% for both parameters (page, per_page), so baseline is 3. The tool description does not add any meaning beyond what the schema already provides.
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 verb 'List' and the resource 'configured data warehouse sources' with examples. However, it does not explicitly differentiate from sibling tools like census_get_source (which gets a single source) or other list tools, though the resource name 'sources' provides implicit distinction.
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 offers no guidance on when to use this tool versus alternatives such as census_get_source (for a specific source) or other list tools. No contextual hints about prerequisites or preferred use cases.
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.