Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Show plan and limits

plan_status
Read-only

What this workspace is paying for: the plan, its status and billing period, the features it unlocks, every numeric limit it carries, and the active add-ons. Where consumption is counted on this side (seats, AI credits) it reports used-vs-limit and flags what is close to its ceiling; a limit whose usage is NOT counted here says so rather than showing zero. Answers 'which plan am I on', 'what am I about to run out of', 'why is a feature unavailable'. Read-only — changing a plan or granting an add-on is never available over MCP.

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

Input Schema

NameRequiredDescriptionDefault
include_featuresNoInclude the full feature matrix (long). Default false — the summary already says how many are on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, non-destructive, closed-world behavior. The description adds valuable output semantics: it reports used-vs-limit where usage is counted, flags limits near their ceiling, and explicitly says uncounted limits are marked rather than shown as zero. The threshold for 'close to its ceiling' is left vague and response format is not detailed, but the added behavioral context is substantial.

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 front-loaded with what the tool reports before moving to consumption semantics, example questions, and the read-only constraint. Every sentence contributes, though the clause about uncounted limits is slightly verbose.

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 read-only status tool with no output schema and one optional parameter, the description covers the returned information, how usage is represented, how missing consumption data is handled, and that mutations are unavailable. An agent has enough context to call it correctly without additional documentation.

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

Parameters3/5

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

There is a single optional parameter, include_features, whose schema description already explains its purpose and default. The tool description does not mention this parameter at all, so it adds no meaning beyond the fully covered schema; baseline 3 is appropriate.

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 states a specific resource (plan, status, billing period, features, limits, add-ons) and a clear reporting purpose. It also distinguishes itself from plan-modification tools by stating that changing a plan or granting an add-on is never available over MCP, though it does not name close siblings such as proc_plan_get.

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?

It gives concrete usage contexts via example questions ('which plan am I on', 'what am I about to run out of', 'why is a feature unavailable'), which tells an agent when this tool applies. It stops short of naming alternatives or stating explicit exclusions, keeping it below a 5.

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

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