Skip to main content
Glama
Sign In

Perq

by sh.perq
OverviewDiscussionsAdmin

Early-access offers (private feed)

early_offers
Read-onlyIdempotent

Offers that are verified but not public yet (embargoed, each with public_after), plus new, changed and closed offer events from the last 30 days, filtered by the subscription topics. Needs the private feed token from subscribe (webhook) or from the email confirmation page.

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": {
      "token": "<token>"
    },
    "name": "early_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesPrivate feed token (starts with pf_).

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantive context: embargo status with a public_after timestamp, a 30-day event window, subscription-topic filtering, and where the token comes from. It does not describe ordering or volume, keeping it short of a 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?

Two sentences, front-loaded with the payload scope before the prerequisite. The dense parenthetical '(embargoed, each with public_after)' earns its place, though the sentence stacks several distinct concepts and could be split for readability.

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 single-parameter read-only feed tool with annotations carrying the safety profile and no output schema, the description covers content, time window, filtering, and credential acquisition. The one real omission is any statement about how this differs from the similarly-scoped recently_changed.

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 would be 3, but the description adds meaning the schema lacks: the token is a private-feed credential obtained either from subscribe (webhook) or the email confirmation page. That provenance is actionable for an agent that does not yet hold a token.

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?

States a specific resource (verified but not-yet-public offers) plus a two-part payload: embargoed offers with public_after and 30-day offer events filtered by subscription topics. This is concrete and distinguishable from get_offer/list_packs, though it never addresses the apparent overlap with the sibling recently_changed.

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?

It gives a real prerequisite (private feed token from subscribe or the email confirmation page), which tells the agent which path this belongs to, but there is no explicit when-to-use versus when-not or an alternative for the 30-day event portion that recently_changed also seems to serve. Usage is implied rather than stated.

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

All Perq 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