Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

subscriptions__get_plan

Retrieves a specific monthly plan and its complete versioned catalog lineage, including seats, entitlements, overage, and MRR.

Instructions

[subscriptions — B2B monthly seats, entitlement quota, overage, and MRR] Get one exact monthly plan and its versioned catalog lineage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>"
    },
    "name": "subscriptions__get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • addedInput schema / properties / plan_id / title
      Added value: +"Plan Id"
    • addedInput schema / title
      Added value: +"get_planArguments"
  2. Changed2 schema fields changedv0.1.9
    • removedInput schema / properties / plan_id / title
      Removed value: -"Plan Id"
    • removedInput schema / title
      Removed value: -"get_planArguments"
  3. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description must disclose all behavioral traits. It only states it's a retrieval operation ('get') without detailing side effects, permissions, rate limits, or return behavior.

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 a single, well-structured sentence with a context tag, making it concise and front-loaded. However, the context tag adds little value.

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

Completeness3/5

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

The description is minimal and does not fully compensate for the lack of output schema or annotations. While it hints at lineage information, the overall completeness is adequate but leaves gaps about response structure.

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

Parameters2/5

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

With 0% schema description coverage, the description fails to explain the 'plan_id' parameter beyond its existence. No details on format, validation, or expected values are provided.

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 clearly states the tool retrieves one exact monthly plan and its versioned catalog lineage, distinguishing it from sibling tools like 'list_plans' which presumably returns multiple plans.

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?

The description implies usage when a specific plan is needed by ID, but does not provide explicit guidance on when to use this tool versus alternatives like 'list_plans' or 'mrr_summary'.

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

Deploy Server

Other Tools