List workspaces
census_list_workspacesRead-only
List workspaces in the organization (note: usually requires an organization-level token). Census: GET /workspaces.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
census
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=true; description adds token requirement and HTTP method (GET), which are useful behavioral details beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler. Front-loaded with action and resource, then adds critical token note and API path.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose, token requirement, and API method. Lacks description of response format (e.g., array of workspace objects), but this is a simple list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has zero parameters, so description does not need to add parameter details. Baseline for 0 params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states verb 'List' and resource 'workspaces' with organization scope. Distinguishes from siblings which target different resources (destinations, models, etc.).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Describes required token type (organization-level), giving usage context. Does not explicitly mention when not to use or alternatives, but siblings list implies this is the only list-workspaces tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness3/5
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.