Skip to main content
Glama

Partizan

Look up a machine price

get_machine_price
Read-onlyIdempotent

Read the published Base USDC ceiling for one owner operation. Example: position-refresh returns 350000 atomic units. This lookup is free.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "position-refresh"
    },
    "name": "get_machine_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYesPublished Partizan owner operation to price.

Output Schema

NameRequiredDescriptionDefault
assetYes
schemeYes
networkYes
operationYesPublished Partizan owner operation to price.
max_objectsNo
maximum_atomicYesAmount in millionths of a USDC.
per_object_atomicNoAmount in millionths of a USDC.

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 read-only, idempotent, non-destructive, closed-world behavior. The description adds genuinely new behavioral context: the returned figure is a ceiling expressed in atomic units, and the call is free (no cost or credit consumption). It does not discuss caching or freshness of the published values, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no filler; the resource and scope come first, followed by a concrete example and the cost note. Each sentence earns its place, though 'Base USDC' unit precision is left for the reader to connect.

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?

An output schema exists, so return structure need not be described, and annotations cover the safety profile. The description supplies cost and unit semantics, making it nearly complete for a single-parameter lookup; only freshness/caching of published prices is unaddressed.

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?

Schema coverage is 100% and the enum is documented, so the schema does most of the work. The description still adds meaning by framing the parameter as selecting one published owner operation and by showing a valid value with its expected return in atomic units, which helps an agent invoke it correctly.

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 names a specific verb and resource: read the published Base USDC ceiling for one owner operation. The example (position-refresh returns 350000 atomic units) makes the output concrete. It is slightly jargon-dependent ('Base USDC ceiling'), and there are no sibling tools to differentiate from, so it falls just short of 5.

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 description implies usage by saying the lookup covers 'one owner operation' and that it is free, which signals a cheap pre-check. It does not explicitly state when to call this versus computing a price another way, and there are no alternatives to name, so guidance remains implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources