Skip to main content
Glama
Sign In
mcp-red-web-utils

mcp-red-web-utils

by hsharmanov02
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

insiders

Retrieve recent SEC Form 4 transactions to track corporate executives' buying and selling. Pay per call in USDC on Base via x402.

Instructions

Latest SEC Form 4 insider transactions (paid per call, USDC on Base via x402)

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that each call is paid via USDC on Base through x402, which is important context. However, it does not describe authentication requirements, rate limits, pagination, or what happens if payment fails.

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?

The description is a single efficient sentence with the core resource front-loaded. Every element—SEC Form 4 insider transactions and the payment mechanism—adds useful information without waste.

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

Completeness3/5

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

For a simple one-parameter retrieval tool, the description covers the data source and payment model. However, it omits the meaning of 'limit' and does not clarify return format or scope, leaving gaps for an agent deciding among edgar-related siblings.

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

Parameters2/5

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

There is one parameter, 'limit,' but the description does not mention it at all, and schema description coverage is 0%. The agent receives no explanation of what 'limit' controls, its expected format, or default behavior.

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?

The description clearly identifies the resource: 'Latest SEC Form 4 insider transactions.' It implies retrieval through 'Latest,' though it doesn't use an explicit verb. It differentiates from siblings like edgar_search by focusing specifically on Form 4 insider transactions.

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?

The description provides no guidance on when to use this tool versus alternatives such as edgar_search or edgar_company. It notes that calls are paid, but does not explain when this tool is preferable or what prerequisites exist.

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