census_list_modelsList SQL models / datasets defined in the workspace (the queries that produce rows to sync). Census: GET /models.
| 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, so the description's mention of the GET endpoint adds minimal value. No additional behavioral traits (e.g., pagination limits) are disclosed beyond the schema.
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?
Two short sentences, no wasted words. Slightly improved structure could separate endpoint info, but overall very concise.
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?
Lacks return value description since no output schema exists. The description explains what is listed but omits details like response fields. Acceptable for a list tool but not comprehensive.
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?
The input schema has 100% coverage with descriptions for page and per_page. The description adds no extra meaning beyond restating the endpoint. Baseline 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 explicitly states it lists SQL models/datasets in the workspace, using a specific verb ('List') and resource ('models'). It distinguishes from siblings like census_get_model (single) and other list tools via clear wording.
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?
No explicit guidance on when to use this tool vs alternatives (e.g., census_get_model for a single model). The description only states what it does, not the context or exclusions.
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.