Skip to main content
Glama
Sign In

Anry

by io.anry.mcp
OverviewDiscussionsAdmin

List opportunities

list_opportunities
Read-onlyIdempotent

What Anry is watching on this site right now: the carded findings the team sees on their own dashboard, highest priority first, each with its subject, stream, live state, estimated impact, and a report id. This is the curated view and stays small by design, so start here for 'what matters now' and call get_report on a row for the full document. Pass since (ISO 8601) to poll for cards that appeared after a moment you have already seen. Quote monetary values verbatim.

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_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO 8601 date or datetime; only findings carded after this instant
site_idYesSite id from list_sites (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower; the description still adds ordering (highest priority first), result size ('stays small by design'), and the fact that rows are curated rather than exhaustive. It does not mention pagination or rate limits, which a polling tool would ideally disclose.

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?

Opening with the concrete scope, then the drill-down, then the polling parameter, is well front-loaded and each sentence carries information. The narrative framing ('What Anry is watching') costs a few words but sets the curated-view expectation.

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?

With no output schema, the description usefully enumerates the row fields (subject, stream, live state, estimated impact, report id) so an agent knows what it gets back. Combined with the get_report drill-down and since semantics, an agent can call this correctly; only pagination/limits are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond the schema by framing since as a polling cursor ('cards that appeared after a moment you have already seen'), which clarifies intent rather than just format. site_id is left to the schema, which is acceptable given full coverage.

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 names the resource precisely ('the carded findings the team sees on their own dashboard') and its scope ('on this site right now'), plus the fields each row carries. It implicitly distinguishes itself from siblings by routing full documents to get_report, though it never names a competing list tool (e.g. list_reports, list_questions) explicitly.

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

Usage Guidelines5/5

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

It states the entry point explicitly ('start here for what matters now'), gives the drill-down alternative ('call get_report on a row'), and explains the polling idiom for the since parameter. Both when-to-use and what-to-do-next are covered.

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