Skip to main content
Glama

Get collection

get_collection
Read-onlyIdempotent

Return a collection and the access/install state of each skill in it.

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
slugYes

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully structured. The description adds one piece of genuine context beyond them, that the payload includes per-skill access/install state, but says nothing about permission requirements for viewing access state, behavior on a missing slug, or scoping of the result.

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?

One sentence, front-loaded with the verb and the returned resource, with the additional payload (per-skill access/install state) packed into a compact clause. Nothing is wasted and nothing is buried.

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?

An output schema exists, so the description needn't explain the return shape, and its one sentence is enough to frame what comes back. However, for a one-parameter lookup with zero schema description coverage, the undefined meaning of 'slug' and the absent not-found/permission behavior leave a real gap.

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 description coverage is 0% for the single required parameter 'slug', so the schema contributes no meaning. The description does not compensate: it never states that the parameter is the collection's slug identifier or that it must be an existing collection, leaving the agent to infer the parameter's role from the word 'collection'.

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 ('Return') and resource ('a collection') and adds scope beyond the name by stating it also returns the access/install state of each contained skill. That distinguishes it in spirit from a bulk lister like list_collections or a single-skill fetch like get_skill, though no sibling is named explicitly.

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 when-to-use guidance: no indication of when to prefer this over list_collections (browsing) or get_skill (single skill detail), and no stated prerequisites such as needing read access to the collection. Usage is only inferable from the return-content sentence.

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