Skip to main content
Glama
Sign In

Form4API — SEC Insider Trading

by io.github.theodor90
OverviewDiscussionsAdmin

get_key_activity

Read-only

Recent, per-request API activity log for the authenticated key. Returns the most recent HTTP requests made with the authenticated API key, most recent first, including the endpoint path, response status code, duration in milliseconds, and timestamp. Use this to debug integration issues — confirm a specific call reached the API, check for repeated 4xx/5xx responses, or spot slow requests — rather than for usage trends; for aggregate daily counts use GET /v1/keys/usage/history instead. Requires a valid X-Api-Key (401 without one). Limited to 30 requests per minute per API key, shared with the other /v1/keys/usage routes (429 KEY_USAGE_RATE_LIMIT).

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of most-recent requests to return. Defaults to 100, maximum 200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint it discloses the auth requirement (401 without X-Api-Key), the 30 req/min rate limit shared with other /v1/keys/usage routes, and the 429 error code, plus ordering (most recent first) and the fields returned. The only gap is retention/window of 'recent' requests, which the agent cannot infer.

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?

Purpose, use cases, exclusion, auth, and rate limit are all front-loaded in a compact block with no filler. It is dense but every clause carries operational value; only the error-code parenthetical borders on excessive detail.

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

Completeness5/5

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

With no output schema, the description enumerates the returned fields (path, status, duration, timestamp) and ordering, and covers auth, rate limiting, and the correct sibling alternative. Nothing needed to invoke or interpret it correctly is missing.

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 single parameter has 100% schema description coverage (limit, default 100, max 200), so the schema already carries the semantics. The description adds nothing about the limit beyond implying recency ordering, so baseline 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 opening sentence names a specific verb and resource ('per-request API activity log for the authenticated key') and immediately scopes it as recent, not aggregate. It distinguishes itself from the sibling/route that handles daily counts, so an agent can route correctly without opening other schemas.

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

Usage Guidelines5/5

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

It states concrete use cases — confirming a specific call reached the API, spotting repeated 4xx/5xx, finding slow requests — and an explicit exclusion: not for usage trends, use GET /v1/keys/usage/history instead. When-to-use, when-not, and the alternative are all named.

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

All Form4API — SEC Insider Trading 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