Skip to main content
Glama

Secant Agent Research Pack

by io.github.jnilrac

codex_audit

Paid x402 Codex audit entrypoint. Use the REST /codex/jobs endpoint to queue execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesCode, configuration, or architecture review prompt for the paid Codex audit.
paymentYesx402 payment proof payload containing resource, amount, wallet, and settlement metadata.
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

C2.5/5.0
Behavior2/5

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

No annotations are provided, and the description is minimal. It does not disclose whether the tool is a read or write operation, side effects, authentication needs, or rate limits. The phrase 'paid' hints at payment but lacks specifics.

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 short but under-specified. It sacrifices clarity for brevity, and the mention of a REST endpoint feels out of place.

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?

Despite having an output schema and full parameter coverage, the description lacks essential context about the tool's workflow, payment handling, and idempotency. It is incomplete for an agent to confidently invoke.

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?

The input schema covers 100% of parameters with descriptions, so the description adds no extra semantic value. Baseline score of 3 is appropriate.

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

Purpose3/5

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

The description identifies the tool as a 'paid x402 Codex audit entrypoint' but does not clearly state what action the tool performs. The reference to a REST endpoint is ambiguous and fails to differentiate this tool from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or avoid this tool. The description mentions using a REST endpoint but provides no context compared to alternatives like extract_page or search.

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