origingrid_listList available information sources, optionally filtered by topic and/or region. Supports limit/offset pagination; the response reports the total number of matches so you can page through all results. [ASRP: Browse available sources by category. Use for exploration before planning.]
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| topic | No | ||
| offset | No | Skip the first N results for pagination | |
| region | No |
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?
With no annotations, the description carries full behavioral disclosure. It explains pagination support (limit/offset, total count), which is good, but does not explicitly state that the operation is read-only or safe, nor mention any authentication or rate limits.
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 concise, with two clear sentences and a bracketed usage hint. Every sentence adds value, and the key purpose is front-loaded.
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?
Given no output schema and low parameter coverage, the description should provide more context. It misses the response structure, what constitutes a 'source,' and how results are identified. The sibling set includes a 'get_source' tool, implying list returns source identifiers, but this is not stated.
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 coverage is low (25%: only offset described). The description adds that topic and region are optional filters and that limit/offset control pagination, but it lacks detail on accepted formats, ranges, or allowed values for topic and region.
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 it lists available information sources with optional filters by topic and region. It distinguishes from search tools like origingrid_search by framing itself as browsing sources, but does not explicitly differentiate from origingrid_get_source.
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 includes a usage hint: 'Browse available sources by category. Use for exploration before planning.' This gives clear context, but it does not mention when to avoid using this tool or suggest alternatives like origingrid_search for content.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.