Skip to main content
Glama

The Valley Desk

List topics and counties

list_topics_and_counties
Read-onlyIdempotent

List the topics and the nine Delaware Valley counties in The Valley Desk directory with the number of listings recorded for each. Use a returned name as the topic or county filter in search.

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_topics_and_counties"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
topicsYes
countiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restatement. The description adds behavior annotations do not carry: the counts are per-listing tallies, and the returned names are valid filter values for search — a real operational fact. It omits nothing critical given that an output schema exists.

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?

Two sentences, with the purpose and scope front-loaded and the downstream usage instruction second; no filler, no restatement of title or annotations.

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 zero-parameter, non-destructive read tool with a full output schema and rich annotations, the description covers purpose, scope, payload, and how to consume the result. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there are no argument semantics to document; the schema is trivially complete at 100% coverage. The description's only obligation is to convey what the empty-argument call yields, and it does that by naming the enumerated dimensions (topics, counties) and the count value.

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 (list topics and the nine Delaware Valley counties) plus the scope and the payload ('the number of listings recorded for each'), which is unusual and distinctive enough that an agent can separate it from search, fetch, and list_institutions without inspecting any schema.

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?

Gives an explicit workflow cue — 'Use a returned name as the topic or county filter in search' — telling the agent this is a discovery step whose outputs feed search. It stops short of saying when this tool is not appropriate versus list_institutions, but the intended call sequence is clear.

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.