Skip to main content
Glama
Sign In

Rightshold

by com.rightshold
OverviewDiscussionsAdmin

Pricing: what Rightshold costs

get_pricing
Read-onlyIdempotent

Use this to see what Rightshold costs before you sign up or plan spend: every pricing line with its price today (0 in the preview) and planned price, its unit and free allowance, and the principles behind the prices — nothing buys placement, a grade, a KYA level, a verdict or a review. No account or key needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "type": "object"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the baseline bar is low. The description still adds real value beyond them: no account or key is required, and prices appear as 0 in preview mode, which is a non-obvious behavioral detail an agent could otherwise misreport to a user.

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?

Front-loaded with the purpose and packed into one sentence with no filler sentences. The em-dash chain of clauses is dense and slightly overstuffed, but each clause (pricing line fields, pricing principles, no auth) carries distinct information.

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

Completeness4/5

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

For a zero-arg, read-only tool with an output schema, the description covers purpose, auth requirements, preview-mode pricing behavior and the guarantees behind the prices — more than enough to call it correctly. The only rough edge is the ambiguous '0 in the preview' phrasing, which assumes the reader knows what preview mode is.

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?

There are zero parameters, so the baseline is 4; nothing about invocation needs explaining. The description correctly spends no words on arguments and instead covers what the response contains.

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?

States a specific verb and resource ('see what Rightshold costs') and enumerates exactly what a pricing line contains: price today, planned price, unit, free allowance. It is unmistakably distinct from sibling tools like sign_up, check_license or issue_rights_manifest, which all act on individual resources.

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?

Gives clear situational context — call it 'before you sign up or plan spend' — which implicitly positions sign_up as the successor action. It does not spell out explicit exclusions (e.g. 'do not use for billing history'), but for a zero-parameter read this leaves little ambiguity.

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

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