Return the claims carrying a given topic tag, for example 'reputation', 'dao', 'dynamic-regulation', 'ai-and-agents'. Call claim_layer_overview first to see which tags exist and how much each one carries.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| topic | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
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 define readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds the important behavior of requiring a prior call to claim_layer_overview, which is not covered by annotations.
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 sentences, front-loaded with the core purpose, example tags, and a crucial usage hint. No extraneous information.
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?
With only two parameters and an output schema available, the description covers all essential information: what the tool does, example inputs, and a prerequisite step. It is complete for this simple tool.
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 description coverage is 0%, but the description provides example values for the 'topic' parameter, aiding understanding. The 'limit' parameter is not described, though its default and purpose are common knowledge. The description partially compensates for the missing schema descriptions.
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 returns claims for a given topic tag, provides example tags, and directs the user to a sibling tool for exploring available tags. This effectively distinguishes it from other tools.
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?
Explicitly instructs users to call claim_layer_overview first to discover valid topic tags and their prevalence, providing clear when-to-use guidance and a necessary prerequisite.
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 or action: overviews, specific claims/papers, searches by different granularities, citation help, and document verification. No two tools overlap in purpose.
All tool names use lowercase snake_case with clear verb-noun or noun-preposition patterns (e.g., get_claim, search_papers, claim_layer_overview). The naming is uniform and predictable.
With 11 tools, the set covers the core operations for exploring a scholarly corpus without being excessive. Each tool serves a clear and necessary purpose.
The tools provide comprehensive coverage for discovering, retrieving, and verifying content from the corpus: overviews, searches at paper/claim/post level, direct retrieval, and document verification. No obvious missing operations for the intended use case.