Skip to main content
Glama
Sign In

Privi Quantum

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Privi Car: what it does

car_info
Read-onlyIdempotent

Privi Car in one call: the tools, record types, key scopes, size limits, prices and safety boundaries.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive, closed-world operation. The description adds useful content scope by listing the categories of information returned, but it does not disclose further behavioral traits such as whether the data is live, versioned, or permission-gated.

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?

The definition is a single front-loaded sentence that immediately identifies the tool's subject and then lists its content categories. Every phrase contributes information, with no redundant or filler wording.

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 informational tool with rich annotations and an output schema, the description supplies the key content categories an agent needs to understand what the call provides. It could explicitly position itself as a discovery step before the car_* action tools, but the essential information is present.

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?

There are zero input parameters and schema description coverage is 100%, so there is no parameter meaning for the description to clarify. The baseline for a parameterless tool is 4, and the description appropriately avoids inventing parameter details.

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 states that the tool returns a consolidated overview of Privi Car and enumerates the content areas it covers: tools, record types, key scopes, size limits, prices, and safety boundaries. This distinguishes it from action-oriented car_* siblings, though it does not use a precise verb such as returns or lists.

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 phrase 'in one call' implies this should be used as a consolidated reference rather than making multiple specific calls, but there is no explicit statement of when to choose it over sibling tools or any prerequisites. The usage is therefore inferable but not clearly directed.

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

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