Skip to main content
Glama

Secant Agent Research Pack

by io.github.jnilrac

research_pack

Paid x402 research pack: search plus extraction and citations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query to run through the paid research API.
paymentYesx402 payment proof payload containing resource, amount, wallet, and settlement metadata.
max_resultsNoMaximum number of ranked search results to return.
extract_pagesNoNumber of top search results to extract for the research pack.
facilitator_idNoSettlement facilitator id. Use evm-base for Base USDC payments.evm-base
payment_identifierNoOptional idempotency key. Reuse it on retries to return the cached paid result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'paid x402' but does not disclose how payment is processed, what happens on failure, or any other behavioral traits (e.g., idempotency via payment_identifier is only in the schema).

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

Conciseness3/5

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

The description is very concise (one sentence) but lacks structure or front-loading. It could be expanded to better serve the agent without being verbose.

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

Completeness2/5

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

Given the presence of an output schema and 100% parameter coverage, the description still lacks completeness. It does not explain the payment process or when to use this tool over free alternatives, leaving gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema; it just says 'search plus extraction and citations' which is already implied by parameters.

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?

The description clearly states it's a paid research pack that includes search, extraction, and citations. It distinguishes from siblings like 'search' (only search) and 'extract_page' (only extraction).

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 it is a paid tool but does not explicitly state when to use it versus alternatives (e.g., the free search tool). There is no guidance on when not to use it or mention of prerequisites like having a wallet for payment.

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

All Secant Agent Research Pack toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Most tools have distinct purposes (audit, extraction, diff monitor, search, combined pack). The research_pack overlaps with search and extract_page but is explicitly a combined tool, so some confusion is possible but descriptions help.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern (codex_audit, extract_page, monitor_diff, research_pack, search). No mixing of styles.

Tool Count5/5

With 5 tools, the set is well-scoped for a research pack. Each tool serves a distinct function without unnecessary bloat.

Completeness4/5

Covers key research actions: search, extraction, diff monitoring, and a Codex audit. A potential minor gap is lack of a tool for managing or storing research results, but core workflows are present.

Resources