Skip to main content
Glama
Sign In

Anry

by io.anry.mcp
OverviewDiscussionsAdmin

List site diary entries

list_diary_entries
Read-onlyIdempotent

The site diary for a window, newest first: what the team and its agents recorded as changed on the site, observed, or withdrawn, each with its subject, date, author and the client that wrote it, its evidence, and whether it was later retracted. Read it before diagnosing a page, a campaign or a move in the numbers: a change inside the window is the first explanation to test, and a fix already shipped is not proposed again. Entries are declared by people, not observed by Anry. Defaults to the last 90 days; at most 365.

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": {
      "site_id": "<site_id>"
    },
    "name": "list_diary_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date, UTC. Defaults to today.
fromNoISO date, UTC. Defaults to 89 days before to.
kindNo
limitNoMax rows to return (default 50)
site_idYesSite id from list_sites (UUID)
subjectNoWhat the entry is about. type page takes the pathname as key (/checkout); campaign takes platform:campaign_id and ad takes platform:campaign_id:ad_id, the subject keys list_reports and list_opportunities print; site takes no key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description's added value is ordering (newest first), the default 90-day window and 365-day cap, and the important caveat that entries are human-declared rather than observed by the system. It omits the default row limit of 50 and any pagination behaviour.

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?

Front-loaded with the resource and ordering, then content, then usage rationale, then constraints. Dense but every clause carries information; the 'declared by people, not observed by Anry' sentence earns its place as an epistemic caveat.

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?

No output schema exists, so the description carries the burden of describing return content, which it does (subject, date, author, client, evidence, retraction flag). Combined with the rich input schema and annotations, an agent has enough to call it correctly; only pagination and row-limit behaviour are left implicit.

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 coverage is 83%, so the schema already explains site_id, subject key formats, kind enum and limit. The description adds only the 90-day default window and the 365-day maximum, which the schema does not state; it says nothing further about kind, subject, or limit semantics. Baseline 3 fits.

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?

States a specific verb and resource ('The site diary for a window, newest first') and enumerates what an entry contains, so the agent knows exactly what comes back. It is clearly the read counterpart to record_diary_entry, though it never names that sibling explicitly.

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 concrete when-to-use guidance: read it before diagnosing a page, campaign or move in the numbers, because a change inside the window is the first explanation to test and an already-shipped fix should not be re-proposed. It stops short of naming alternatives or stating when not to call it.

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

All Anry 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