Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

List plans

list_plans
Read-onlyIdempotent

The plans for sale, with price and term, and the account's active plan. Each purchase lasts 30 days, with no automatic renewal. Each purchase lasts 30 days, with no automatic renewal. Without an account or wallet credential, account is null. Daily monitoring requires an account and its e-mail. Claim a wallet purchase after sign-in to use it there. Active Starter, Pro and Agency plans also include agent prompts for that account, within 60 requests/hour.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safe, read-only, idempotent, closed-world profile, and the description adds real behavior: 30-day terms with no auto-renewal, `account` being `null` without credentials, and a 60 requests/hour ceiling for agent prompts on Starter/Pro/Agency. That is meaningful context beyond the structured hints, though it omits any pagination or response-shape notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose well, but the sentence 'Each purchase lasts 30 days, with no automatic renewal.' appears verbatim twice, which is obvious waste. The remaining sentences are dense but each carries distinct information about credentials and rate limits.

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 and no parameters, the description does the necessary descriptive work by naming the key returned concepts (price, term, active plan, nullable account) and the conditions attached to them. The main remaining gap is guidance on how this differs from `pricing` and when to follow up with `buy_plan`.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no filtering input is needed and instead explains the credential conditions that affect what `account` contains.

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 resource: the plans available for purchase with price and term, plus the account's active plan. That is clear enough to distinguish it from `buy_plan` or `cancel_plan`, but it never explicitly contrasts with the `pricing` sibling, which could plausibly return overlapping information.

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 statement of when to call this versus `pricing`, `buy_plan`, `cancel_plan`, or `prompt_allowance`. The closest thing to guidance is indirect, for example the notes about needing an account for daily monitoring and claiming a wallet purchase after sign-in, but the agent must infer the routing itself.

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

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