Skip to main content
Glama

Tally by Outpost

List sites

list_sites
Read-onlyIdempotent

The site this API key reads: its id, name, domain, time zone and how visitors are counted (cookie, cookieless or consent).

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

Input Schema

NameRequiredDescriptionDefault
siteNoThe site's id. Optional: the API key's site is the one read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 value beyond them by disclosing the shape of the payload (id, name, domain, time zone, counting mode) — important because there is no output schema. It does not cover error behavior for an invalid site id.

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?

A single compact sentence that front-loads the scope ('the site this API key reads') and then enumerates the returned fields. The parenthetical '(cookie, cookieless or consent)' is a dense, high-value detail. Slight deduction for being a verbless fragment that never says 'returns'.

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 one-optional-parameter read tool with no output schema, the description is adequate: it enumerates the returned fields and explains the default subject of the read. Missing is any hint about how this output is used downstream by sibling analytics tools, which would help an agent sequence calls.

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 single optional `site` parameter is fully documented there, including the pattern and the default behavior. The description's phrase 'the site this API key reads' only echoes that default; it adds no syntax or format meaning. 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 states exactly what is returned — the single site the API key reads, with its id, name, domain, time zone and visitor-counting mode. This usefully clarifies that 'list_sites' behaves singularly (only the key's own site is exposed), which an agent could not infer from the plural name alone. It stops short of naming an explicit verb or differentiating it from the analytics siblings.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the metadata/lookup tool used to discover site identity and configuration. There is no statement of when to call it (e.g., 'call first to resolve the site id used by other tools') and no exclusion or alternative named. All guidance about the optional parameter lives in the schema, not the description.

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