Skip to main content
Glama

Rams review quota

usage
Read-onlyIdempotent

Check how many Rams reviews this account has used and how many are left. Free to call. It does not use a review.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planNoPlan name
usedYesReview credits used in the window
limitYesReview credits included; null = unlimited
windowYes"lifetime" (free reviews that do not renew), "billing_cycle" (an account set to pause at its limit) or "rolling_30_days"
pausedNowNoAn account set to pause at its limit: true while paused
remainingYesIncluded credits left; null = unlimited
resumesAtNoAn account set to pause at its limit: when the next billing cycle starts (ISO 8601)
fullReviewsNoPresent when full reviews are capped; past the cap review_files returns a quick check
overageBillingNoPresent where it applies: true = reviews past the limit keep running and are billed on the monthly invoice
purchasedCreditsYesPurchased review credits, spent automatically once the included ones run out

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / fullReviews / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "fullReviews": {
      +      "additionalProperties": true,
      +      "description": "Present when full reviews are capped; past the cap review_files returns a quick check",
      +      "properties": {
      +        "cap": {
      +          "type": "number"
      +        },
      +        "used": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "used",
      +        "cap"
      +      ],
      +      "type": "object"
      +    },
      +    "limit": {
      +      "description": "Review credits included; null = unlimited",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "overageBilling": {
      +      "description": "Present where it applies: true = reviews past the limit keep running and are billed on the monthly invoice",
      +      "type": "boolean"
      +    },
      +    "pausedNow": {
      +      "description": "An account set to pause at its limit: true while paused",
      +      "type": "boolean"
      +    },
      +    "plan": {
      +      "description": "Plan name",
      +      "type": "string"
      +    },
      +    "purchasedCredits": {
      +      "description": "Purchased review credits, spent automatically once the included ones run out",
      +      "type": "number"
      +    },
      +    "remaining": {
      +      "description": "Included credits left; null = unlimited",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "resumesAt": {
      +      "description": "An account set to pause at its limit: when the next billing cycle starts (ISO 8601)",
      +      "type": "string"
      +    },
      +    "used": {
      +      "description": "Review credits used in the window",
      +      "type": "number"
      +    },
      +    "window": {
      +      "description": "\"lifetime\" (free reviews that do not renew), \"billing_cycle\" (an account set to pause at its limit) or \"rolling_30_days\"",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "used",
      +    "limit",
      +    "remaining",
      +    "window",
      +    "purchasedCredits"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety profile adds nothing. What the description adds beyond them is genuinely useful and not in the structured data: the billing/quota consequence of calling it ('Free to call. It does not use a review.'). It says nothing further about rate limits or freshness of the quota figures, which keeps it from a 5.

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?

Three short sentences, front-loaded with what it returns. 'Free to call' and 'It does not use a review' restate the same cost trait twice, so one of the two is mildly redundant, but there is no filler beyond that.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and with no parameters the schema burden is nil. For a zero-arg read tool the description covers purpose, cost and non-consumption, which is everything an agent needs to call it correctly.

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 there is no parameter meaning to convey and the baseline is 4. The description correctly implies the account context is implicit rather than passed in.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check how many Rams reviews this account has used and how many are left'), including the exact scope of the numbers returned. The clause 'It does not use a review' implicitly contrasts it with the review-consuming siblings (quick_review, review_files, review_url), so an agent can separate it without opening a schema.

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 a clear selection cue by declaring the call is free and consumes no quota, which signals it is the safe pre-check before invoking a review tool. It stops short of an explicit 'use this before X instead of Y' statement or any exclusion, so it is strong but not fully prescriptive.

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