Skip to main content
Glama

Rams

by ai.rams.worker
OverviewDiscussionsAdmin

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.

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. 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"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context beyond the annotations: the call is free and consumes no review quota, which is the crucial side-effect distinction for this tool.

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?

Three short sentences, front-loaded with what the tool reports and followed by the cost/side-effect caveat. Every sentence carries information the agent needs; nothing is padding.

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?

For a zero-parameter, read-only quota check with an output schema and full annotation coverage, the description supplies everything needed: what it returns, that it is free, and that it does not consume quota. Return-value detail is correctly left to the output schema.

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. There is nothing for the description to disambiguate, and it correctly does not invent parameter detail.

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?

The description states a specific verb and resource: checking how many Rams reviews this account has used and how many remain. The line 'It does not use a review' distinguishes it from the review-consuming siblings (quick_review, review_files, review_url), so an agent can tell it apart without opening the 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?

'Free to call. It does not use a review.' gives clear context for when this is safe to invoke versus the consuming siblings, which is the key decision an agent faces here. It stops short of explicitly naming an alternative or stating a when-not condition, so it is clear 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.

All Rams toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources