Skip to main content
Glama

Get collection

get_collection
Read-onlyIdempotent

Quality-ranked tools inside one curated collection. Critical-risk tools are excluded by default (risk_filter); every result carries risk_level and risk_reasons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
limitNo
risk_filterNoRisk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levelsexclude_critical
include_high_riskNoDeprecated alias for risk_filter=none

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
resultsYes
collectionYes
total_in_collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "collection": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "slug": {
      +          "type": "string"
      +        },
      +        "tagline": {
      +          "type": "string"
      +        },
      +        "title": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "slug",
      +        "title",
      +        "tagline"
      +      ],
      +      "type": "object"
      +    },
      +    "count": {
      +      "type": "number"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "category": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "composite_score": {
      +            "type": "number"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "is_official": {
      +            "type": "boolean"
      +          },
      +          "last_commit_at": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "platforms": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "profile_url": {
      +            "type": "string"
      +          },
      +          "quality_score": {
      +            "type": "number"
      +          },
      +          "repo_url": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "risk_level": {
      +            "type": "string"
      +          },
      +          "risk_reasons": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "stars": {
      +            "type": "number"
      +          },
      +          "tier": {
      +            "enum": [
      +              "curated",
      +              "promising",
      +              "experimental",
      +              "review_required"
      +            ],
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "slug",
      +          "tier",
      +          "quality_score",
      +          "composite_score",
      +          "risk_level",
      +          "risk_reasons",
      +          "type",
      +          "category",
      +          "platforms",
      +          "description",
      +          "repo_url",
      +          "profile_url",
      +          "stars",
      +          "is_official",
      +          "last_commit_at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total_in_collection": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "collection",
      +    "total_in_collection",
      +    "count",
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • removedInput schema / properties / include_high_risk / default
      Removed value: -false
    • addedInput schema / properties / include_high_risk / description
      Added value: +"Deprecated alias for risk_filter=none"
    • addedInput schema / properties / risk_filter
      Added value: +{
      +  "default": "exclude_critical",
      +  "description": "Risk gate: exclude_critical omits critical risk (default); exclude_high omits high and critical risk; none omits no risk levels",
      +  "enum": [
      +    "exclude_critical",
      +    "exclude_high",
      +    "none"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: the default risk_filter behavior (excluding critical risk) and that every result carries risk_level and risk_reasons. This goes beyond annotations without contradicting them.

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?

The description is a single, dense sentence that front-loads the core purpose (curated, quality-ranked collection) and then the key behavior (risk filtering). No wasted words; every phrase adds value.

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

Completeness4/5

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

Given the output schema exists (so return values are defined), annotations cover safety, and the description explains the critical risk_filter behavior, the definition is nearly complete. It doesn't mention pagination or sorting, but limit is in the schema. The only gap is not explicitly routing to siblings, but that's covered by usage guidelines and overall context is sufficient.

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

Parameters3/5

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

Schema description coverage is 50% (risk_filter and include_high_risk have descriptions, slug and limit do not). The description explicitly mentions risk_filter and its default behavior, partially compensating. Slug is an enum with clear values and limit has min/max in the schema, so they are self-explanatory. The description adds some value but does not fully cover all parameters.

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 the tool returns a curated, quality-ranked collection of tools, and explicitly mentions the risk filtering default and the presence of risk_level/risk_reasons fields. This distinguishes it from siblings like search_skills (searching) and list_collections (listing all collections), making the purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies when to use it (when you want a curated, quality-ranked set of tools from a collection) but does not explicitly state alternatives or exclusions. The sibling list suggests potential confusion, but no direct 'use this instead of X' guidance is provided. It's adequate but not explicit.

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.