Skip to main content
Glama

get_revenue_plan

Read-onlyIdempotent

Read immutable collaborator shares for a capability. No plan means seller receives 100%, platform fee 0 in this trial release.

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": {
      "capability_id": "<capability_id>"
    },
    "name": "get_revenue_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
capability_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, and the description adds value beyond them by disclosing that shares are immutable and what the fallback economics are when no plan exists. It does not say what the returned share structure looks like, so the transparency is good but not complete.

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?

Two short sentences with the core action front-loaded and no redundant padding. The second sentence is dense but carries genuinely distinct information about the default case.

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?

For a single-parameter read with no output schema, the description should at least sketch what a 'collaborator share' record contains or what the unknown-capability response is. It covers the no-plan default but leaves the normal return shape and error behavior unstated, so an agent can invoke it but cannot predict its payload.

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?

With only one parameter at 0% schema description coverage, the description carries the burden, and 'for a capability' only loosely identifies capability_id as the capability whose plan is read. It adds no format, lookup, or validation meaning (e.g., whether an unknown ID errors or returns the default 100% case).

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: 'Read immutable collaborator shares for a capability,' which tells an agent exactly what is retrieved. It stops short of distinguishing itself from the sibling set_revenue_plan (the write counterpart), so the read/write pairing must be inferred from the names.

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 by the read framing and the sibling set_revenue_plan, but the description never states when to call this instead of that or when a plan must exist first. The default-behavior sentence ('No plan means seller receives 100%...') is useful context but is not explicit routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources