Skip to main content
Glama

Tally by Outpost

Attribution coverage

get_coverage
Read-onlyIdempotent

How much of the period's revenue is attributed to a visitor, by method, and the fix-it list for what isn't (with code to paste).

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

Input Schema

NameRequiredDescriptionDefault
toNoA custom range's last day (YYYY-MM-DD), with from.
fromNoA custom range's first day (YYYY-MM-DD), with to. Up to 366 days, not past today.
siteNoThe site's id. Optional: the API key's site is the one read.
periodNoA preset period, in the site's time zone. Leave out for the tool's default, or give from and to instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds useful return-shape context — coverage share by method and a remediation list with paste-able code — but never says how coverage is computed or what the response payload looks like in detail.

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?

One compact sentence that front-loads the core metric before the secondary fix-it list. The nested parentheticals make it slightly dense but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry return-value burden, and it only sketches the shape (share by method plus a remediation list). For a four-parameter analytics tool with zero required params and a default period, more detail on what the response contains and how to interpret 'coverage' would help.

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 clear date-range constraints, the optional site fallback to the API key's site, and the period enum, so the schema does the heavy lifting. The description only implies that a period/range scopes the revenue figure and adds nothing on 'method' semantics.

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 gives a concrete verb-plus-resource: it reports what share of period revenue is attributed to a visitor, split by attribution method, plus a remediation list. That is substantive and distinguishable from siblings like get_overview or get_breakdown, though it never explicitly contrasts with them.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The phrase 'fix-it list for what isn't' hints at a diagnostic use case, but an agent gets no signal about when this beats get_breakdown or whether prerequisites (e.g., tracking setup) apply.

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