Skip to main content
Glama

SouthPow crypto & market data

buy_insider_OCFC

Paid. OCFC insider BUYS from SEC Form 4 (open-market purchases by officers, directors, 10% owners), as filed. $0.01 USDC on Base. No account, no API key. URL https://southpow.media/v1/insider-buys/OCFC.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1-100 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: it is a paid call ($0.01 USDC on Base), requires no account or API key, and reflects Form 4 filings 'as filed.' It stops short of explaining how payment is actually transacted or what happens on payment failure.

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 cost qualifier 'Paid.' is front-loaded, followed by the data definition, then payment/access, then the endpoint URL. Every clause carries distinct information with no filler.

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 paid, single-parameter data tool with no output schema, the description covers the data definition, cost, auth model, and endpoint. It does not describe the returned record shape or how pagination/limit interacts with the response, and gives no hint of the payment handshake an agent must perform to complete the call.

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?

There is only one parameter (limit) and the schema already documents it fully at 100% coverage ('Rows, 1-100 (default 20)'). The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 states a specific resource (OCFC insider BUYS), names the exact data source (SEC Form 4) and narrows the transaction type to open-market purchases by officers, directors, and 10% owners. That specificity immediately distinguishes it from a generic insider tool or a different ticker sibling.

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 pricing, payment chain, and 'no account, no API key' notes make the cost/access model clear, which implicitly tells the agent when this is viable. However, there is no explicit when-to-use or when-not guidance, and no mention of alternatives such as the generic buy_insider tool or other ticker variants.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources