Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Look up a category

find_categories
Read-onlyIdempotent

Look up a single Google Maps category by name (French or English), with its number of places. To build a target, use suggest_categories instead; use this only to check or add one category id to search.categories.ids.

Free.

Same call as GET /api/v1/categories of the REST API.

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

Input Schema

NameRequiredDescriptionDefault
qNoCategory name, French or English (empty: the most frequent categories).
limitNoCategories returned (default 20, at most 50).
countryNoCounts are those of this country (default fr).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 genuinely non-structured context: the call is free (cost/quota signal) and maps 1:1 to GET /api/v1/categories, which helps an agent reason about caching and billing. It stops short of describing ordering of results or how counts are scoped beyond the country default.

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?

Front-loaded with purpose, followed immediately by the sibling routing rule. The standalone 'Free.' sentence and the REST-endpoint note are short and each carry a distinct signal, though the REST reference is of marginal value to an agent that only calls the MCP tool.

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 small three-parameter, zero-required, no-output-schema lookup, the description covers purpose, alternative routing, cost, and the return content ('its number of places'). Nothing critical is missing, though it could state whether results are ordered by frequency or relevance.

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 all three parameters (q, limit, country) are already documented, including the empty-q behavior and the country default of 'fr'. The description restates the French/English name aspect but adds no syntax, ranking, or matching semantics beyond the schema, so the baseline of 3 applies.

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: look up a Google Maps category by name in French or English, returning place counts. It clearly differentiates itself from suggest_categories. The only flaw is calling it 'a single' category while the schema's limit parameter (default 20) implies a ranked list is returned, a small internal inconsistency.

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?

Explicitly names the alternative ('To build a target, use suggest_categories instead') and the precise condition for choosing this tool ('only to check or add one category id to search.categories.ids'). An agent has no ambiguity about routing between the two.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Primavera toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources