get_collection
Fetch a curated collection of blocks. Costs 0.5 credits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| collection_id | Yes |
PromptDNA
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It mentions cost (0.5 credits) but lacks details on side effects, authentication, rate limits, or return format. Incomplete for a fetch operation.
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?
Single sentence is concise but sacrifices informative detail. Could be slightly longer to include essential behavioral notes without being verbose.
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?
With 1 param, no output schema, and no annotations, the description omits critical context: what constitutes a 'curated collection', response structure, error handling, or pagination. Incomplete for an API tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage for parameters. Description only implicitly indicates collection_id is an identifier but adds no explicit format, constraints, or examples beyond the schema field name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Fetch a curated collection of blocks', which is a specific verb+resource. It distinguishes from siblings like get_block (single block) and search_blocks (search).
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 on when to use this tool vs alternatives. While cost is mentioned, there is no context about prerequisites or scenarios where this tool is preferred.
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.