Skip to main content
Glama

Mastering Financial Markets

MFM account quota status

quota_status
Read-onlyIdempotent

Read-only: how many complete company pages this MFM account can still read (first 30 days: 10 profiles per day and 30 companies per month; then 10 every 5 minutes, 40 per day and 100 companies per month (UTC day and month; shared by website and AI)) and how many selections (40 per calendar month, shared with the website), with reset times (UTC). Nothing is consumed. Clients that only expose search and fetch get the same answer from search with the query "quota" or from fetch with the id "quota".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this with 'Nothing is consumed' plus the exact quota windows and shared-with-website/AI semantics. Reset times in UTC and the sharing model are genuinely useful behavioral context beyond the annotations, though 'selections' is never defined.

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?

Everything is crammed into one long sentence with triple-nested parentheses enumerating rate limits, which makes the key facts hard to scan. The size is defensible given the quota complexity, but the structure is not front-loaded beyond the initial 'Read-only' cue.

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

Completeness4/5

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

With zero parameters, no output schema and fully covered annotations, the description supplies the remaining substance: what counters exist, their limits, their scope (UTC, shared with website and AI), and that reset times are returned. Only the meaning of 'selections' is left unexplained.

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 takes no parameters, so the baseline is 4; there is nothing for the description to disambiguate. It does not need to compensate for any schema gap.

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 states a specific resource and what is reported: remaining complete company pages and remaining selections, plus reset times for an MFM account. It is a clear read-status tool, though the core purpose is buried inside dense nested parentheticals about rate limits, which slows recognition of the verb+resource.

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

Usage Guidelines4/5

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

It tells the agent this is a read-only check that consumes nothing, and explicitly routes clients that only expose search/fetch to the equivalent 'quota' query or id. It stops short of stating the trigger condition (e.g. check before screening companies to avoid exhausting limits), so it is strong context without full when-to-use guidance.

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