Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Ask for more permissions

request_scopes
Read-onlyIdempotent

Get a single-use link where the user approves extra permission tiers for this connection. After they approve, retry the refused action. API keys keep the tiers they were made with: for a key, create a new one with create_api_key instead.

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": {
      "tiers": "<tiers>"
    },
    "name": "request_scopes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiersYesPermission tiers: read, write, destructive, billing, account, team, connections, support, keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: the returned artifact is a single-use link, approval is performed by the user out-of-band, and API keys cannot be re-scoped, only recreated. That is the multi-step escalation workflow an agent cannot infer 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the primary action and return artifact, then the follow-up step, then the exception. Every sentence carries a distinct, load-bearing instruction with no filler.

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 one-parameter tool with no output schema and full annotation coverage, the description covers the trigger, the returned link, the user-approval step, the post-approval action, and the API-key exception. An agent can invoke it correctly and knows what to do next without opening the schema.

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?

Schema coverage is 100% and the tiers enum is fully spelled out in the schema, so the description need not restate it. The phrase 'extra permission tiers for this connection' clarifies that the tiers are additive and connection-scoped, but adds little beyond what the schema already enumerates. Baseline 3 applies.

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 first sentence states a specific verb (get) and resource (a single-use approval link) and scopes it to this connection's permission tiers. It is clearly distinguishable from siblings like create_api_key and from read-only listers such as list_granted_scopes.

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

Usage Guidelines5/5

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

Explicit trigger-and-follow-up guidance: call it when an action was refused, have the user approve, then retry the refused action. It also names the exclusion and the alternative — for an API key, use create_api_key with the desired tiers instead of escalating this key.

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

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