Skip to main content
Glama
Sign In
edgar-mcp

edgar-mcp

by asp53826
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cache_stats

Check the current session's cache hit rate, request count, and bytes downloaded to gauge data retrieval efficiency.

Instructions

Cache hit rate, request count, and bytes downloaded this session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It clarifies the scope ('this session') and the metrics reported, implying a read-only operation. However, it does not explicitly state that there are no side effects, nor explain any session lifecycle or reset behavior. Still, it adds meaningful context beyond a bare tool name.

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 sentence that lists the three key metrics without any filler. Every word is informative, and it is front-loaded with the primary output (cache hit rate).

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?

The description is adequate for a simple, parameterless stats tool. It names the metrics and the session context. However, it lacks detail on the return format or how 'session' is defined, which could be ambiguous. Given no output schema, a bit more context might help, but it is not critically incomplete.

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

Parameters4/5

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

The tool accepts zero parameters, and the schema provides 100% coverage with no fields to document. The description does not need to explain parameters, and it does not. The baseline for zero parameters is 4.

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 tool as providing cache hit rate, request count, and bytes downloaded for the current session. It specifies the exact resource (cache statistics) and distinguishes it from sibling tools that deal with concepts, filings, and companies.

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 guidance is provided on when to use this tool or when to prefer alternatives. It does not mention exclusions or specific scenarios where cache_stats would be appropriate. The description implies it is for monitoring session performance, but this is not explicitly stated.

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