Skip to main content
Glama

VarynForge

by com.varynforge
OverviewDiscussionsAdmin

Get account status

get_account_status
Read-only

Get the operator account status — the organization whose plan/credits/limits this payload describes (plans and usage limits are per-organization; see list_organizations), current plan, available credits, brief quota state, the lint_draft daily verification cap (applies on every tier; check lint_drafts_remaining_today before a verification loop), the idea_checks allowance (check_idea is daily- AND monthly-capped on every tier; check remaining before a check loop), locked paid tools, the upgrade URL, and next_actions: the ranked cross-project queue of what to do next. Defaults to the personal organization; pass organizationId when working a project that belongs to a different organization — its shared caps are the ones project actions consume. Read on session start and after a wall hit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesOne sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose.
organizationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "context"
+]
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / organizationId
      Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With readOnlyHint=true already provided, the description adds substantial behavioral context: it defines the organization scope of the payload, per-organization caps, the lint_draft daily cap applying on every tier, and the cross-project next_actions queue. This goes well beyond the annotation and helps the agent understand the tool's data semantics and operational timing.

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?

The description is dense but front-loaded with the core purpose, and every parenthetical serves a concrete operational purpose, such as referencing list_organizations or checking remaining allowances. It is longer than average, but the enumeration of return fields and usage caveats earns the length.

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?

Given there is no output schema, the description must carry the burden of explaining what the tool returns, and it does: plan, credits, quota, caps, locked tools, upgrade URL, next_actions, plus the default-organization behavior and when to pass organizationId. It is fully actionable for an agent deciding whether and how to call this tool.

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 schema describes the context parameter clearly, but organizationId only has length constraints with no semantic description. The description compensates by explaining that organizationId selects the organization whose caps apply, and defaults to the personal organization. This is meaningful added meaning, though the context parameter's semantics are primarily carried by the schema.

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 opens with a specific verb ('Get') and resource ('account status'), then enumerates the exact fields returned: plans, credits, quota state, lint_draft cap, idea_checks allowance, locked tools, upgrade URL, and next_actions. This level of specificity clearly distinguishes it from sibling tools like list_organizations and get_changelog.

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?

The description explicitly states when to call it: 'Read on session start and after a wall hit.' It also explains when to pass organizationId ('when working a project that belongs to a different organization') and directs the user to check allowance fields before verification/check loops, giving actionable routing guidance.

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

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