Skip to main content
Glama

Get collection

get_collection
Read-onlyIdempotent

Returns collection metadata, sections, visible content, share_url, and the revision for the next write. share_url is null when the collection link is unavailable.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world semantics, so the description only needs to add beyond that. It does: it discloses the conditional null behavior of share_url when the collection link is unavailable, and explains that the response carries the revision token required for the next write, which is genuinely useful workflow context.

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, zero filler, and the return contents are front-loaded before the share_url edge case. Every clause carries information an agent cannot get from the schema or annotations.

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

Completeness3/5

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

With no output schema, the description does the work of listing return fields, which is appropriate, and it flags one null case. It still leaves open what 'visible content' means (likely permission-dependent), what happens on a missing or unauthorized collection_id, and what collection_id itself should be.

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?

There is one required parameter (collection_id) with 0% schema description coverage, and the description says nothing about it — no format, no source, no indication whether it is an ID, slug, or handle. With low coverage the description is expected to compensate, and it does not.

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 uses a specific verb (Returns) and resource (collection), and enumerates the payload: metadata, sections, visible content, share_url, and the revision for the next write. It is clear what the tool does, though it never contrasts itself with siblings such as list_collections.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The phrase 'the revision for the next write' faintly implies a read-before-write/optimistic-concurrency workflow, but this is left for the agent to infer rather than stated.

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