Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Figures of a search

get_search_metrics
Read-onlyIdempotent

The figures of a search in one call: total, places with an email address, a phone number, a website, and the estimated number of email addresses.

Free.

Same call as POST /api/v1/search/metrics of the REST API.

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": {
      "search": "<search>"
    },
    "name": "get_search_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchYesThe search, as returned by POST /categories/suggest (field "search"). Send it back as is, edited if needed. The "search" object returned by suggest_categories (target, area, filters, sort), sent as is or edited; its full schema is the "search" input of count_search. An invalid search is refused with invalid_request and the fields to fix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — that the call is free — plus the fact that all figures come back in a single call. It does not explain rate limits, the precision of the 'estimated' email figure, or whether results reflect cached/indexed data.

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 returned values are front-loaded in the first sentence, with supporting context (cost, REST equivalent) after. The 'Free.' fragment is terse but informative; the REST endpoint mapping is of marginal value to an agent but costs only one line.

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?

There is no output schema, so the description correctly carries the return-value burden by enumerating each figure produced. The single nested parameter is fully specified in the schema, and the free-call and REST-equivalence notes round out what an agent needs before invoking it.

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 nested 'search' object is documented in detail, including its origin from suggest_categories, its relationship to count_search, and the invalid_request failure mode. The description adds no parameter-level meaning beyond that, so the baseline 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?

The description names a specific resource ('the figures of a search') and enumerates exactly what is returned: total, counts of places with email/phone/website, and an estimate of email addresses. An agent can tell it is a metrics/summary read rather than a listing or count, though it never explicitly contrasts itself with count_search or preview_search.

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?

The only usage signal is 'Free.', which hints at cost but says nothing about when this tool should be chosen over count_search, preview_search, or estimate_list. There is no when-not guidance and no stated prerequisites beyond the schema's implicit dependency on a search object.

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