Skip to main content
Glama
Sign In
Zearch MCP

Zearch MCP

Official
by zearchcomputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Zearch pricing

get_pricing
Read-onlyIdempotent

Retrieve Zearch’s public price list to check credit costs per request type, plans, and top-ups without an API key.

Instructions

The public Zearch price list: credits per request type, plans and top-ups. Free; no API key needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real context beyond them: the data is public, costs nothing, and requires no API key or authentication, which is exactly what an agent needs before deciding a preflight call is cheap.

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 no filler: the content of the price list is front-loaded and the access conditions follow. Every clause carries information an agent can act on.

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?

For a no-parameter, read-only lookup with no output schema, the description covers what the tool returns, that it is public, and that it needs no credentials. Nothing required to invoke or interpret it is missing.

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 meaning to convey; the baseline for a no-arg tool applies. The description does usefully scope what the parameterless response contains (credits, plans, top-ups).

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 resource ('the public Zearch price list') and enumerates its contents (credits per request type, plans, top-ups). None of the siblings (get_run, get_wallet, list_runs, research, verify) cover pricing, so an agent can select this tool without ambiguity.

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 by the described contents rather than stated: an agent must infer it should call this when it needs cost/plan information. No alternatives or exclusions are named, but the narrow, obvious scope of a pricing lookup limits the risk of misselection.

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