Skip to main content
Glama

privi_network_access_information

Read-only

Shows Privi's published human-review pricing and limitations for paid API access so you can assess costs and constraints without checkout, credentials, entitlements, or external paid actions.

Instructions

Show Privi's published human-review pricing and limitations on paid API access. No checkout, API credential, entitlement, or external paid action is created.

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_access_information"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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, so the safety profile is known. The description adds genuinely new behavioral context by enumerating the side effects that do NOT occur — no checkout, no credential issuance, no entitlement grant, no external paid action — which tells an agent it can call this freely without triggering commerce.

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 short sentences with zero filler, and the substantive content (what is shown) is front-loaded ahead of the disclaimer. 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?

For a zero-parameter, read-only information tool with no output schema, the description covers what is retrieved and what is not triggered. The one gap is that it does not characterize the shape of the returned information (e.g., pricing tiers vs. a limitations list), which matters since no output schema exists to fill that in.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs, and it correctly implies a no-argument call.

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?

The description pairs a specific verb ("Show") with a specific resource: Privi's published human-review pricing and limitations on paid API access. It is clearly not the service-directory sibling, since the subject is pricing/limitations rather than services. It falls short of 5 only because the sibling is not named explicitly for routing.

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?

Usage is implied rather than stated: an agent can infer this is the tool to consult for cost and restriction information before touching paid access. The negative clause ("No checkout, API credential, entitlement, or external paid action is created") usefully rules out expectations of a purchase flow, but there is no explicit when-to-use or when-not-to-use guidance relative to the service directory.

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