Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Account, credits and limits

get_account
Read-onlyIdempotent

Retrieves your NewsCatcher plan, credit balance, search limits, and rate limits so you can check capacity before large jobs or troubleshoot 402, 403, and 429 errors.

Instructions

Your NewsCatcher plan, credit balance and limits: credits per search effort, results per call, how far back each endpoint reaches, and rate limits. Free. Use it before large jobs, when a call fails with 402/403/429, or to explain costs.

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly/ idempotent / openWorld, so the bar is lower; the description still adds real value by declaring the call is free (no credit consumed) and by enumerating what limits are reported. It does not mention caching or whether the values are live, which would have earned a 5.

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?

Two sentences with zero padding. The returned fields are front-loaded, then actionable triggers, which is the right order for an agent scanning for a reason to call.

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?

There is no output schema, so the description must carry return semantics, and it does list the fields an agent will receive. It stops short of stating the response shape or units (e.g. whether history depth is days or months), a minor residual gap for a no-param, no-output-schema tool.

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 there is nothing to disambiguate; the baseline is 4. The description correctly signals a parameterless call rather than implying filters exist.

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 names a concrete resource set - plan, credit balance, per-search credit cost, results per call, per-endpoint history depth, and rate limits - so an agent knows exactly what comes back. It lacks an explicit verb and does not name a sibling, but the content is clearly distinct from the search/research siblings.

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?

Gives three concrete invocation triggers: before large jobs (cost pre-check), after 402/403/429 failures (diagnosis), and when explaining costs to a user. These are the exact situations where plan/limit data changes behavior, and no other tool would serve them.

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