Skip to main content
Glama

Little Works

discover_browse_places

Places with active Discover listings (live when callable available).

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

Input Schema

NameRequiredDescriptionDefault
modeNoprojects|requests|recipes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it says essentially nothing about return contents, ordering, pagination, or auth. The phrase 'active Discover listings' implies a filtered subset, which is the one useful behavioral hint, but 'live when callable available' is unexplained and does not clarify availability semantics.

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?

It is a single short sentence, so nothing is bloated, but the parenthetical is cryptic filler rather than front-loaded scope. Brevity here comes at the cost of substance rather than from efficiency.

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

Completeness2/5

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

With one optional parameter, no output schema, and no annotations, the description is the only source of semantics, yet it never explains what a 'place' record contains or how mode values map to results. An agent could not confidently predict the response or decide between this and the other discover_* tools.

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 single 'mode' parameter is documented in the schema itself ('projects|requests|recipes'), which sets the baseline at 3. The description adds nothing about what mode changes or how it interacts with 'places', and notably the schema's value list looks incongruent with a places-listing tool, leaving an agent to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase ('Places with active Discover listings') rather than a verb+resource statement of what the tool retrieves or returns. It does not distinguish this tool from siblings such as discover_search, discover_browse_types, or list_materials_places, and the parenthetical '(live when callable available)' adds ambiguity rather than specificity.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives: no mention of discover_browse_types, discover_search, or list_materials_places, which appear to overlap. The only conditional clause ('live when callable available') is opaque and does not tell an agent under what circumstances the tool should be selected.

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