Skip to main content
Glama

Vercel OSS Registry

List filter values

list_facets
Read-onlyIdempotent

Values (with project counts) for a filter: topic, language or cohort. Use to pick valid search_projects filters.

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": {
      "facet": "<facet>"
    },
    "name": "list_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
facetYes
limitNo

Output Schema

NameRequiredDescriptionDefault
facetYes
totalYes
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioral fact — that each value comes with a project count — but says nothing about how the count relates to the default result cap or whether results are truncated at the limit.

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

Conciseness4/5

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

Two sentences, no filler, with the value-plus-counts detail front-loaded ahead of the usage hint. The compression is close to over-terse, but nothing in the text is wasted.

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 return-value structure need not be described. However, for a tool with a paging/size parameter and an empty schema description, the definition should at least explain what 'limit' caps and whether counts reflect the full corpus; that omission leaves a real hole.

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%, so the description must carry parameter meaning. It merely restates the facet enum already present in the schema and adds no meaning for 'limit' (default 40, max 200), which is undocumented in both places. The one parameter that actually needs explanation is the one left unexplained.

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?

States a specific outcome (facet values with project counts) and enumerates the three facet kinds, which lets an agent tell it apart from search_projects and get_project. It is terse and never uses a full verb such as 'return' or 'list', but the intent is unambiguous.

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?

'Use to pick valid search_projects filters' names the downstream consumer and the exact situation that calls for this tool, which is genuine when-to-use guidance. It stops short of stating when not to use it (e.g., that it does not itself return projects), so it is not a full 5.

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.