Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Quote Data Store Run

alterlab_store_quote
Read-onlyIdempotent

Quote a listing run: price per valid result, markup, and the maximum cost for max_results. The maximum is a hard cap; only valid results are billed and the rest is refunded. Free and keyless; this never reserves or debits anything. To run, call alterlab_store_run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "alterlab_store_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesListing slug, e.g. from alterlab_store_search
versionNoPin a major version, e.g. 1
max_resultsNoMaximum valid results to buy (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real billing semantics on top: maximum is a hard cap, only valid results are billed, the remainder is refunded, and nothing is reserved or debited. That is exactly the context an agent needs before spending, stated explicitly rather than left to inference.

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?

Four short sentences, front-loaded with what is priced, then the billing guarantee, then the next-step tool. No filler and no repetition of the schema.

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 three-parameter read-only quote with full schema coverage and no output schema, the description covers cost semantics, safety, and the follow-up call. The only soft spot is that the exact shape of the returned quote is implied rather than described.

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 goes further by framing max_results as a hard cost cap with a refund for invalid results, which tells the agent how the parameter drives spend. It does not clarify the version pinning behavior, so it stops short of a 5.

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?

Specific verb (quote) and resource (a listing run), plus the exact outputs quoted: price per valid result, markup, and maximum cost for max_results. The closing sentence names the sibling alterlab_store_run, so the agent can distinguish quote from execute without opening either schema.

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?

Clearly positions this as the pre-flight step and routes the agent to alterlab_store_run to actually execute. The gap is that the sibling alterlab_estimate_cost also exists and the description gives no rule for choosing between quoting a listing run and estimating cost.

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

All mcp-server 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