Skip to main content
Glama
Sign In
ProxyAPI-Perplexity

ProxyAPI-Perplexity

by spolperim-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Статус запроса и расходы Perplexity

perplexity_check
Read-only

Check Perplexity request status by job_id—running, completed with answer, or error—or list recent requests, today's spend, and remaining balance without user permission.

Instructions

Бесплатно (без обращения к модели) показывает статус запроса по job_id: идёт, готово (с ответом) или ошибка. Без job_id — список последних запросов, расходы за сегодня и остаток баланса. Разрешение пользователя не нужно.

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

Input Schema

NameRequiredDescriptionDefault
job_idNoНомер задачи из ответа perplexity_search / perplexity_research

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond readOnlyHint/openWorldHint: the call is free, does not invoke the model, requires no user permission, and enumerates the possible status outcomes including the error case. These are exactly the operational facts an agent needs before polling repeatedly.

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 tight sentences, front-loaded with the cost fact ('Бесплатно'), then the two modes, then the permission note. Slightly dense but every clause carries information; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one optional parameter, no output schema, and annotations already covering the safety profile, the description covers both invocation modes and the shape of what comes back well enough to call it correctly.

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%, so the baseline is 3, but the description adds meaning the schema lacks: job_id originates from a perplexity_search / perplexity_research response, and omitting it switches the tool into an aggregate mode rather than returning nothing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('показывает статус запроса по job_id') and enumerates the exact states returned: in progress, done with answer, or error. It also states a second mode (no job_id → recent requests, today's spend, balance) and clarifies it does not invoke the model, which cleanly separates it from perplexity_search / perplexity_research.

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?

Gives clear conditional usage: pass job_id to poll a specific task, omit it to get recent requests plus cost and balance. What's missing is an explicit statement that this tool never starts a search and that perplexity_search / perplexity_research should be used for that — the routing is only implied by 'без обращения к модели'.

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

Deploy Server

Other Tools