Skip to main content
Glama

List DSSR posts

get_dssr_locations
Read-onlyIdempotent

Returns a paginated list of every DSSR post with its country, ISO code and post name; q filters by case-insensitive substring. total counts every match regardless of offset and limit. Use it to find the exact post name for the by-location tools when the country is unknown; get_dssr_locations_by_country is shorter when it is known. Returns no rates.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch by name
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/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 the safety profile is covered. The description adds real context beyond that: pagination, the fact that `total` counts all matches regardless of `offset`/`limit`, and the negative disclosure "Returns no rates" that prevents misuse as a rate lookup. It doesn't state the result ordering or page-size ceiling (max 20).

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?

Three dense clauses, each carrying distinct information: return shape, filter/count semantics, and routing to the alternative. The negative constraint "Returns no rates" is a short, high-value closer with no filler.

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

Completeness5/5

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

For a 3-parameter, no-output-schema list tool, the description covers what is returned, how filtering and counting work, and when to prefer a sibling. No output schema is present, yet the return fields are enumerated, leaving no material gap for correct invocation.

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 only 33% (only `q` has a description, as bare "Search by name"), so the description must compensate and largely does: it specifies that `q` is a case-insensitive substring filter and explains how `total` relates to `offset`/`limit`. It still doesn't document defaults or the `limit` maximum of 20, which remain schema-only.

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?

States a specific verb and resource ("Returns a paginated list of every DSSR post") plus the exact fields returned (country, ISO code, post name). It also distinguishes itself from the sibling get_dssr_locations_by_country, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ("find the exact post name for the by-location tools when the country is unknown") and names the alternative with the condition that selects it ("get_dssr_locations_by_country is shorter when it is known"). Nothing is left to inference.

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