Skip to main content
Glama

List filter vocabularies

get_reference
Read-onlyIdempotent

Canonical tokens for the status, entitlementStatus, and requestTypes filters. facet is required: "statuses", "entitlementStatus" (the body groups and statuses that make a "council:approved" style pair), or "requestTypes" (the 15 application types, each with its early, middle, or late stage). Does not use credits.

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": "get_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
facetYesWhich vocabulary to list. entitlementStatus returns the body groups and statuses that make up an entitlementStatus pair; requestTypes returns the application types with the stage of each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / facet / description
      Previous value: -"Which vocabulary to list."New value: +"Which vocabulary to list. entitlementStatus returns the body groups and statuses that make up an entitlementStatus pair; requestTypes returns the application types with the stage of each."
    • changedInput schema / properties / facet / enum
      Previous value: -[
      -  "statuses",
      -  "decisionBodies",
      -  "requestTypes"
      -]New value: +[
      +  "statuses",
      +  "entitlementStatus",
      +  "requestTypes"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile needs no restating. The description adds genuinely new behavior: no credit consumption, and per-facet return contents (body-group/status pairs, 15 application types with stage).

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

Conciseness3/5

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

Dense but front-loaded, with the required facet constraint stated early. The three-way parenthetical breakdown repeats much of what the enum descriptions already say, so a portion of the text does not earn its place.

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?

For a single-parameter, read-only reference lookup with no output schema, the definition covers required input, the meaning of each facet value, and the shape of returned content. What remains missing is only routing guidance against sibling reference tools.

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% and the enum values are already documented, yet the description still adds meaning: it gives a concrete 'council:approved'-style pair example and specifies that requestTypes carry early/middle/late stages. Minor redundancy with the enum descriptions keeps it below 5.

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 names the exact resource (canonical tokens for the status, entitlementStatus, and requestTypes filters) and enumerates the three facets, so an agent knows precisely what it returns. It does not explicitly contrast itself with the similar-sounding get_permit_reference sibling, leaving a small differentiation gap.

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?

Usage is largely implied: this is the lookup to call before applying one of those three filters, and facet is stated as required. The only explicit guidance is the cost note 'Does not use credits', with no when-not-to-use case or named alternative for other reference needs.

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