Advanced tool. List all registered data sources for this org with their schema summaries. Use this to discover available tables before calling query_data or register_source.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default 1). | |
| limit | No | Results per page (default: all visible sources, max 200 when set). |
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?
No annotations are provided, so the description must disclose all behavioral traits. It fails to mention that the tool is read-only, requires certain permissions, or has any rate limits. The listing nature implies non-destructiveness but is not explicitly stated.
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 only two sentences, front-loading the purpose and then adding usage guidance. Every word is necessary.
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?
Without an output schema, the description mentions 'schema summaries' but does not explain what fields are returned. For a listing tool, more detail on the response structure would improve completeness.
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?
Both parameters are fully described in the schema with clear descriptions. The description adds no additional meaning beyond what the schema already provides, meeting the baseline for high coverage.
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 all registered data sources with schema summaries, and explicitly distinguishes its use from query_data and register_source, making its purpose unambiguous.
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 provides explicit context to use this tool before calling query_data or register_source, but does not mention when not to use it or list other alternatives beyond those two siblings.
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.
Most tools target distinct resources or actions, but there is some overlap (e.g., run_repository_fix vs run_repository_pipeline vs simulate_repository) that could cause confusion. Overall, descriptions help differentiate.
Tool names are primarily snake_case with a verb_noun pattern, but there are inconsistencies (e.g., single-word verbs like 'simulate', 'tokenize', and mixed prefixes like 'preview_', 'product_'). The pattern is readable but not uniform.
With 140 tools, the server is extremely over-scoped for typical MCP usage. This overwhelms agents and suggests poor separation of concerns, likely violating the principle of minimal tool surfaces.
The tool set covers a wide range of functionalities including data onboarding, simulation, decisions, repository management, and admin operations. Minor gaps exist (e.g., no update_agent_run), but core workflows are well-supported.
