Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Subscriptions report

subscriptions_report
Read-only

Server-side aggregation of the caller's ACTIVE recurring spend. Returns active_count, monthly_total (every period normalized to a monthly equivalent), yearly_total (= monthly × 12) and a by_category breakdown of monthly totals. Read-only, single-currency phase-1 (the 'currency' field is the distinct currency, or 'mixed' when active subscriptions span several).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: every period is normalized to a monthly equivalent, yearly_total is derived as monthly × 12, and the currency field is either a distinct currency or the literal 'mixed' when subscriptions span several. That normalization rule is behavior an agent cannot get from the schema or annotations.

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 tight sentences, front-loaded with what is aggregated and scoped, then outputs, then caveats. The trailing currency parenthetical is slightly dense but every clause carries information; 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?

No output schema exists, so the description must carry the return contract — and it does, naming all four returned fields and explaining the derivation of yearly_total and the meaning of the currency value. Combined with annotations covering read-only behavior, an agent has everything needed to call and interpret 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?

Zero input parameters, so the baseline is 4 and there is nothing for the description to disambiguate on the input side. The description instead spends its words on output semantics, which is appropriate here.

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 verb and resource — 'server-side aggregation of the caller's ACTIVE recurring spend' — with scope qualifiers (caller-scoped, active-only) that separate it from a raw listing tool like list_subscriptions. It does not name an alternative explicitly, but the aggregation-vs-listing distinction is unambiguous from the wording.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for totals rather than per-subscription rows, but there is no explicit 'use this when… / use list_subscriptions when…' guidance or any prerequisite note. Adequate for a zero-parameter report tool, but leaving routing to inference.

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