get_block_versions
Changelog for a block's lineage. Costs 0.5 credits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lineage_id | Yes |
PromptDNA
TDQS
C2.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions the credit cost (0.5 credits) but fails to disclose other important behaviors such as idempotency, error handling, or data scope. With no annotations, the description carries the full burden and is insufficient for safe invocation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (two sentences) and front-loads the purpose. However, it is too sparse for the complexity of the tool; it sacrifices essential details for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, output schema, and any parameter details, the description leaves major gaps. It does not specify what the return value looks like, how lineage_id is obtained, or common use cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single required parameter lineage_id has no description in the schema, and the tool description does not explain what it represents or how to find it. Schema description coverage is 0%, and the description adds no value to parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a changelog for a block's lineage, indicating it returns historical versions. This distinguishes it from siblings like get_block (current version) and fork_block (create new version). However, the term 'lineage' is not fully explained, slightly reducing clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like get_block or find_compatible_blocks. The description only states what it does, not the context or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct action or resource. For example, compose_prompt assembles prompts, search_blocks searches, register_agent initiates registration. Even related tools like get_block and get_block_versions are clearly differentiated by purpose (current vs history).
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., compose_prompt, submit_block, verify_registration). No mixing of naming conventions, making it predictable for an agent.
Tool Count4/5
With 20 tools, the scope is broad but well-justified by the diverse functionality (search, submission, ratings, registration, DMCA, etc.). It is on the higher end but not excessive for a full-featured platform.
Completeness3/5
The tool set covers core workflows like searching, viewing, creating, and rating blocks, but lacks update or delete operations for blocks. Also missing tools for managing user profiles or block editing, which are notable gaps.