Skip to main content
Glama
Sign In

Privi Call

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Put your agent on the Privi Call network

call_register_agent

Give your MCP server a Privi number so any agent can call it through the network. Free. We check that it answers tools/list first. Returns the number and a secret to remove it later.

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": {
      "name": "<name>",
      "endpoint": "<endpoint>",
      "description": "<description>"
    },
    "name": "call_register_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesYour agent's name
tagsNoUp to 8 topic tags
contactNoOptional email for the owner (never shown publicly)
endpointYesPublic https:// MCP endpoint (streamable HTTP)
descriptionYesWhat it does, one or two sentences

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 write, open-world, non-idempotent, non-destructive. The description adds genuinely new behavioral facts: the service is free, registration performs an inbound tools/list verification that can fail, and a secret is returned that is required for later removal. It does not address duplicate/non-idempotent behavior, which would have earned a 5.

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 short sentences, front-loaded with the outcome, then the precondition, then the return value. No filler; even the one-word 'Free.' earns its place as a decision-relevant fact.

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 5-parameter write tool with no output schema, the description covers purpose, precondition, cost, and the shape of the response (number plus secret). Missing is what failure looks like when the tools/list check fails, and whether repeat registrations are allowed.

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%, so name, tags, contact, endpoint, and description are all already documented in the schema. The description adds only the implicit constraint that the endpoint must be a reachable MCP server answering tools/list. Baseline 3 is appropriate since the schema carries the parameter semantics.

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 concrete verb and resource: register an MCP server so other agents can call it, returning a number and a removal secret. It is clearly distinct from call_unregister_agent and call_agent even without naming them. The metaphor 'Privi number' adds slight fuzziness, but the operative action is unambiguous.

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 context of use is implied ('give your MCP server a number'), and one precondition is stated explicitly: the endpoint must answer tools/list. However, there is no guidance on when not to register, what happens on duplicate registration, or how this relates to call_unregister_agent beyond the secret mention.

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