Retrieve a paginated list of all dashboards for a project by providing the project ID or name.
List all dashboards for a project.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | No | Project ID. Must be a number (integer), not a string. | |
| projectName | No | Project name (alternative to projectId). | |
| page | No | Page number, 0-based. Must be a number (integer), not a string. | |
| size | No | Page size. Must be a number (integer), not a string. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Lacks any behavioral context (e.g., pagination, authentication, side effects). Annotations absent, so description fails to compensate.
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?
Single sentence, no wasted words, but misses important details.
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?
Four parameters with pagination, no output schema; description lacks pagination details and return structure.
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 covers 100% of parameter descriptions; description adds no extra meaning beyond that.
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?
Description uses specific verb 'List' and resource 'dashboards', scoped to 'for a project'. Clearly distinguishes from sibling list tools for other resources.
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 guidance on when to use vs alternatives, no prerequisites or exclusions provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/iampopovich/allure-testops-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server