Skip to main content
Glama

privi_network_service_directory

Read-only

Locate current Privi MCP endpoints and Glama listings for Ledger, Verify, Anchor, Quantum, Call, or Agent Survival; returns discovery details only, without invoking, paying, or granting access.

Instructions

Find current Privi Ledger, Verify, Anchor, Quantum, Call or Agent Survival MCP endpoints and their Glama listings. This is informational discovery only; the tool does not invoke, pay for, or grant access to commercial services.

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

Input Schema

NameRequiredDescriptionDefault
service_idNoOptional exact Privi service identifier; omit to return all six distinct hosted MCP services.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds value by stating the tool performs no invocation, payment, or access grant, confirming a pure lookup with no side effects. It could go further on whether the listings are cached/static versus live-fetched, but the safety profile is well covered.

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 filler: the capability comes first, then the scope limitation. Nothing is repeated and nothing could be trimmed without losing routing signal.

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-required-param, read-only lookup with a fully described enum, the definition gives enough to call it correctly. With no output schema, it only loosely sketches the return (endpoints plus Glama listings), leaving the agent to discover the actual response shape at call time.

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 single service_id parameter already has an enum plus a description of omitting it to return all six. The description restates the same six service names but adds no new semantics such as format, matching case, or behavior on invalid ids, so this is baseline territory.

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?

"Find current Privi ... MCP endpoints and their Glama listings" gives a specific verb (find) and resource (endpoints/listings), and enumerates the six services it covers. It does not name or contrast with the sibling privi_network_access_information, so the agent must infer the split.

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?

The description clearly frames the tool as "informational discovery only" and explicitly excludes invoking, paying for, or granting access to commercial services, which tells the agent when this tool is the wrong choice. It stops short of naming the sibling tool as the alternative for those other operations.

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