Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Look up a brand or network

find_networks
Read-onlyIdempotent

Look up a brand, franchise or network by name. Use its id in search.filters.networks ({ "mode": "only" | "exclude", "ids": [...] }); mode "exclude" without ids removes every known network (independent businesses only).

Free.

Same call as GET /api/v1/networks 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": {
      "q": "<q>"
    },
    "name": "find_networks"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesBrand or network name ("Century 21", "McDonald's").
limitNoNetworks returned (default 10, at most 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld=false, so safety is covered. The description adds genuine context beyond that: the call is free and corresponds to GET /api/v1/networks, plus the semantic gotcha of empty "exclude" mode. It says nothing about result size or how partial/ambiguous name matches are resolved.

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?

Front-loaded verb+resource in the first sentence, then the integration guidance, then cost and REST equivalence in short standalone lines. No filler; every sentence carries information.

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?

With no output schema, the description usefully explains the shape of what comes back (ids consumable by search.filters.networks) and notes cost. The main remaining gap is how matching works for ambiguous brand names and how many results to expect by default, though limit's schema entry partly covers the latter.

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%, with both q and limit fully documented including defaults and bounds, so the baseline is 3. The description adds no extra meaning for either parameter — its only added detail concerns the id values produced, not the inputs.

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+resource ("Look up a brand, franchise or network by name") and immediately explains the payoff of the call: the id for use in search.filters.networks. An agent can distinguish this network-lookup from area/category lookups without opening the 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 clear downstream context — use the returned id in search.filters.networks with mode "only" or "exclude" — and flags the edge case that "exclude" with no ids removes every known network. It does not explicitly contrast with sibling finders like find_areas or find_categories, so the when-not-to-use guidance is absent.

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