Skip to main content
Glama

Staats

by io.github.MrViolets

List annotations

list_annotations
Read-only

Recorded deploy/change markers, newest first. period defaults to '90d'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNothe site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
periodNorelative period like '7d', '90d' (default)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
periodYes
annotationsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint=true annotation already covers safety. The description adds meaningful behavioral context by stating that results are returned newest first and that period defaults to '90d', which are not visible in annotations and enrich the agent's expectations.

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?

Two short sentences with no filler. The core resource and ordering are front-loaded, and the period default is stated in the second sentence. Every word earns its place.

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?

The tool is simple with two optional parameters and an output schema provided. The description covers the key concept and ordering, while the schema explains site and period. Nothing essential is missing for correct invocation.

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 period default is already documented in the schema. The tool description repeats the default but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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 identifies the resource as 'Recorded deploy/change markers' and notes the ordering 'newest first', which is specific and useful. It does not explicitly differentiate from siblings like what_changed or record_annotation, but the resource phrase is enough to convey the list operation.

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 implied: an agent can infer that this tool retrieves annotation history. However, there is no explicit guidance on when to prefer it over alternatives like what_changed or what_broke, nor mention that record_annotation is the write counterpart.

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

All Staats toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target clearly distinct resources or analytic questions: site CRUD, annotation handling, overviews, funnels, journeys, and diagnostic checks are separated. A few tools like get_overview, query, and what_changed could overlap when asking 'what happened', but their descriptions differentiate the intended use well.

Naming Consistency3/5

The CRUD tools follow a clean verb_noun pattern (create_site, delete_site, list_sites, update_site_context), but analysis tools mix bare nouns (funnel, journeys), bare verbs (query), adverb-verb compounds (compare_around), and what_* question phrases (what_broke, what_changed). Naming is readable and snake_case is consistent, but the overall convention is not uniform.

Tool Count5/5

15 tools is within the well-scoped range and each tool earns its place: site management, annotation tracking, traffic overview, discovery, diagnostics, and comparison all have dedicated tools. There is no obvious redundancy or padding.

Completeness4/5

The surface covers the core domain well: sites can be created, listed, deleted, and contextualized; annotations can be recorded and listed; analytics support overview, breakdown, funnel, journey, and anomaly questions. Minor gaps exist such as no update/delete for annotations and no single-site getter separate from list_sites, but agents can work around these.

Resources