Skip to main content
Glama

List directory

list_directory
Read-onlyIdempotent

List curated directory listings (schema 1.2.0). Optional filters: q, category, tag. Education only, not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional free-text query matched against listing id, name, category, description and tags (case-insensitive). Omit to return all listings.
tagNoOptional exact tag to filter by (case-insensitive), e.g. self-custody or nostr. Omit for all tags.
categoryNoOptional exact category name to filter by (case-insensitive), e.g. Hardware wallet or Nostr client. Omit for all categories.

Output Schema

NameRequiredDescriptionDefault
countYes
listingsYes
disclaimerYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "count": {
      +      "type": "integer"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "listings": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "last_reviewed": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "license": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "related_pillars": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "risk_notes": {
      +            "oneOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              }
      +            ]
      +          },
      +          "sponsored": {
      +            "type": "boolean"
      +          },
      +          "tags": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "url": {
      +            "type": "string"
      +          },
      +          "verification": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "category",
      +          "url",
      +          "description",
      +          "sponsored",
      +          "tags",
      +          "verification",
      +          "last_reviewed",
      +          "risk_notes",
      +          "license"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "schema_version": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "disclaimer",
      +    "schema_version",
      +    "count",
      +    "listings"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional exact category name to filter by (case-insensitive), e.g. Hardware wallet or Nostr client. Omit for all categories."
    • addedInput schema / properties / q / description
      Added value: +"Optional free-text query matched against listing id, name, category, description and tags (case-insensitive). Omit to return all listings."
    • addedInput schema / properties / tag / description
      Added value: +"Optional exact tag to filter by (case-insensitive), e.g. self-custody or nostr. Omit for all tags."
  3. 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, closed-world behavior, so safety is covered. The description adds a schema version marker (1.2.0) and a content-scope caveat, which is modest extra context but says nothing about result size, pagination, or ordering. Appropriate but not rich beyond the annotations.

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 short sentences, front-loaded with the resource and filter list. The trailing disclaimer is marginal but very brief and does not obscure the core information.

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 values need not be explained, and all three optional parameters are documented in the schema. What is missing is the navigation context: when to browse with this versus searching via 'search_directory'. Adequate for a simple read tool but with a clear gap.

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 100%, so the schema already explains q, tag, and category thoroughly, including case-insensitivity and omit-to-return-all behavior. The description merely restates the parameter names without adding matching semantics or combination rules. Baseline 3 applies when the schema carries the detail.

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 verb and resource ('List curated directory listings') plus the filter dimensions and a schema version. It is clear what the tool does, but it never mentions the sibling 'search_directory', so an agent cannot tell from the description alone whether listing or searching is the intended path.

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 only usage signals are that filters are optional and the mention of 'search_directory' is absent, leaving the list-vs-search choice to inference. 'Education only, not financial advice' is a content disclaimer rather than a when-to-use rule. The description implies a browse-everything mode but does not say so explicitly.

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