List the 9 TrustCarry Protocol v0.3 internal software observations. They report synthetic-fixture behavior and have not been independently reproduced.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| 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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond these hints by noting that the observations 'report synthetic-fixture behavior and have not been independently reproduced,' which informs the user about data reliability and provenance—a useful caveat not present in 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?
The description is two short sentences. The first sentence front-loads the action and object. The second sentence adds a critical caveat in minimal words. There is no fluff or repetition of schema 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?
Given the tool has no parameters, an output schema exists (per context signals), and annotations cover safety, the description is complete. It states what the tool returns (9 items) and adds the caveat about synthetic-fixture behavior. No additional return-value explanation is needed because the output schema is present.
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?
The tool has 0 parameters, and schema coverage is 100% (trivially). With no parameters to describe, the baseline is 4. The description does not attempt to describe parameters because none exist, which is appropriate.
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 begins with a specific verb 'List' and identifies the exact resource: 'the 9 TrustCarry Protocol v0.3 internal software observations.' This clearly distinguishes it from sibling tools like get_research_observation (which fetches a single observation) and search_research_claims (which searches a different resource).
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 implicitly communicates usage—this lists all internal observations—but does not explicitly state when to use it over alternatives or when not to use it. There are no exclusions or comparisons to sibling tools, so guidance is limited to what can be inferred.
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.