Skip to main content
Glama
Sign In

Privi Call

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Call an agent

call_agent

Call a tool on any agent on the Privi Call network and get its answer, with a sealed call record. Free to Privi agents; other agents 50 free calls a day, then $0.001 each from a call key.

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": {
      "number": "<number>",
      "tool": "<tool>"
    },
    "name": "call_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool name on that agent (call_list_tools)
numberYesNumber of the agent to call (call_directory)
paymentNox402 payment for a paid target tool; forwarded as _meta['x402/payment']
call_keyNoPrepaid call key (pck_...) for calls past the free 50 a day
argumentsNoArguments for that tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false, so the safety profile is covered. The description adds genuinely new behavioral context: per-day free quotas, per-call pricing, the call_key mechanism, and a 'sealed call record' artifact. It does not explain failure behavior when the remote tool errors, which is a notable gap for an open-world tool.

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?

Two sentences, zero waste, with the core verb and resource front-loaded before the cost/eligibility detail. Every clause carries 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?

No output schema, but the description says what comes back ('its answer, with a sealed call record'), and cost/eligibility for a 5-param tool is covered. Left unclear: what a sealed record contains and how to retrieve/verify it (call_log / call_verify_log exist), and error semantics.

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 description coverage is 100%, including prerequisites ('call_list_tools', 'call_directory'), x402 payment forwarding, and call_key format. The description adds nothing about parameters beyond this, so baseline 3 applies.

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 ('Call a tool on any agent on the Privi Call network') and the outcome ('get its answer, with a sealed call record'). This clearly separates it from sibling registration/billing tools, though it never names an alternative explicitly.

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?

No explicit when-to-use vs alternatives, but the pricing/eligibility clause ('Free to Privi agents; other agents 50 free calls a day, then $0.001 each from a call key') implicitly tells the agent it needs a call_key or payment past the free tier. Prerequisite tools (call_list_tools, call_directory) are named only in the schema, not the description.

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

All Privi Call 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