Skip to main content
Glama

Codenation

Get a collection

get_collection
Read-onlyIdempotent

Get one Codenation collection by slug (as returned by list_collections): its introduction and each tool with a short price and the date that price was checked. Returns an error result if the slug is unknown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCollection slug, e.g. "best-auth-tools-for-saas".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety needs no repetition. The description earns credit for adding behavior the annotations don't carry: the exact contents of the response (introduction, per-tool price, date the price was checked) and the explicit error-result outcome for an unknown slug. It says nothing about auth requirements or freshness guarantees, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both load-bearing: the first defines the lookup and its return payload, the second defines failure behavior. The identifying information (what is fetched, keyed by what) is front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description fully compensates by describing the returned structure and the error case. For a single-parameter lookup tool with complete annotation coverage, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the schema already documents the slug with a concrete example. The description goes one step beyond by tying the value's provenance to another tool's output ("as returned by list_collections"), which tells the agent where a valid slug comes from rather than just its format.

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 gives a specific verb and resource ("Get one Codenation collection by slug") and immediately enumerates the payload: the introduction plus each tool with its short price and price-check date. That level of specificity clearly separates it from list_collections (which supplies the slugs) and from get_tool, so an agent can pick it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes the precondition well by noting the slug comes "as returned by list_collections", which tells the agent to enumerate first and fetch second. It also covers the failure path (unknown slug returns an error result). It stops short of explicitly excluding alternatives such as search_tools for keyword-driven discovery, so it is clear context rather than full when/when-not guidance.

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.

Resources