Skip to main content
Glama

find_site

Read-onlyIdempotent

Resolve a site name or controller ID to exact matches, returning candidates and flagging ambiguous results so you can choose the correct site.

Instructions

Resolve a human site name or exact ID without guessing.

Returns every matching candidate. If more than one site matches, the result is explicitly marked ambiguous so the caller can choose an exact site.

Args: name: Site name or controller ID. Exact ID match wins first, then exact name match (case-insensitive), then falls back to a substring match. Multiple hits are never auto-picked — check ambiguous in the result and call again with a more specific name or the exact id from sites. cursor: Opaque pagination token copied from a previous response's next_cursor. Omit on the first call. limit: Max matches to return in this page. Omit to use the server default page size (50; max 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSite name or controller ID. Exact ID match wins first, then exact name match (case-insensitive), then falls back to a substring match. Multiple hits are never auto-picked — check `ambiguous` in the result and call again with a more specific name or the exact `id` from `sites`.
limitNoMax matches to return in this page. Omit to use the server default page size (50; max 200).
cursorNoOpaque pagination token copied from a previous response's `next_cursor`. Omit on the first call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds substantial behavioral context: exact matching precedence, case-insensitivity, substring fallback, no auto-picking of ambiguous results, and cursor-based pagination. This goes well beyond the structured annotations.

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?

The description is well-structured with a clear opening sentence and an organized Args section. It is slightly verbose, but every detail about matching precedence and pagination earns its place, and it is front-loaded with the core purpose.

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?

Given the presence of an output schema, the description correctly focuses on non-obvious behaviors: ambiguity handling, matching precedence, and pagination. It fully covers the tool's complexity with no missing critical context.

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 description essentially repeats the same parameter details found in the schema (name, cursor, limit). It adds no new semantic meaning beyond what is already structured, so the baseline 3 applies.

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?

The description uses a specific verb "Resolve" with a clear resource (site) and explicitly states the tool returns matching candidates without guessing. It distinguishes itself from sibling tools like find_element and find_resource by focusing on site name/ID resolution.

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?

The description clearly states when to use the tool (to resolve a site name or exact ID) and gives explicit follow-up guidance for ambiguous matches: check the 'ambiguous' flag and call again with a more specific name or exact id. It does not explicitly name alternatives, but the context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamdheerajdubey/prisma-sdwan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server