Skip to main content
Glama

Get directory listing

get_listing
Read-onlyIdempotent

Get a single directory listing by id. Education only, not financial advice.

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": {
      "id": "<id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDirectory listing id from list_directory, e.g. monero-project

Output Schema

NameRequiredDescriptionDefault
siteYes
listingYes
disclaimerYes
criteria_urlYes
generated_atYes
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": {
      +    "criteria_url": {
      +      "type": "string"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "generated_at": {
      +      "type": "string"
      +    },
      +    "listing": {
      +      "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"
      +    },
      +    "schema_version": {
      +      "type": "string"
      +    },
      +    "site": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "schema_version",
      +    "generated_at",
      +    "site",
      +    "criteria_url",
      +    "disclaimer",
      +    "listing"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Listing id, e.g. monero-project"New value: +"Directory listing id from list_directory, e.g. monero-project"
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered by structured data. The description adds only the notion of a single-record lookup; the trailing "Education only, not financial advice" is a legal disclaimer rather than behavioral disclosure about lookup semantics, missing-record behavior, or auth needs.

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?

The operative sentence is front-loaded and waste-free at a single clause. The second sentence is a disclaimer with little selection value, which keeps it from a 5 but does not bloat the definition.

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 one-parameter read tool with full schema coverage, complete annotations and an output schema (so return values need not be described), the definition is essentially sufficient. The only modest gap is the absence of explicit routing guidance toward list_directory or search_directory.

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% and the single parameter already documents its source and gives a concrete example (monero-project), so the schema carries the parameter semantics. The description adds nothing beyond restating that lookup is by id, which is the appropriate baseline when the schema does the heavy lifting.

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 and resource ("Get a single directory listing by id"), and the word "single" plus the id requirement distinguishes it from the sibling list_directory. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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 only implied: an agent can infer this is the tool to call when it already has a listing id, and that list_directory/search_directory are the ways to obtain one. There is no explicit when-to-use or when-not-to-use statement, and no alternatives are named in the description itself.

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