Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Get company lists

get_company_list
Read-onlyIdempotent

Retrieve a saved company list with each company's identification status (ready, resolving, not_found), or return all saved lists when no list ID is provided.

Instructions

Show one saved company list with each company's identification status (ready, resolving, not_found…), or with no list_id, all your lists. Free.

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

Input Schema

NameRequiredDescriptionDefault
formatNotext
list_idNoThe list to show; leave out to list all lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, so the safety profile is covered; the description adds genuine value beyond that by enumerating the identification status values ('ready, resolving, not_found…') an agent will see and flagging the call as 'Free'. It does not mention pagination or result size, which is a minor remaining gap.

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?

A single sentence that front-loads the primary mode and then the fallback mode; every clause (status values, no-list_id behavior, cost) carries information. No filler.

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?

For a two-parameter read-only tool with no output schema, the description covers the resource, both invocation modes, the status vocabulary, and cost. The main omission is any mention that a format parameter controls text vs. json output.

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?

Schema coverage is 50%: list_id is documented in the schema and restated in the description, adding little, while the 'format' enum (text/json, default text) is not explained anywhere in the description. Baseline 3 is appropriate, though the format gap keeps it from going higher.

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?

States a specific verb ('Show') and resource ('saved company list'), and clarifies the two modes: one list by id, or all lists when list_id is omitted. It does not name a sibling alternative (e.g. save_company_list / edit_company_list), but the read framing distinguishes it implicitly from the mutating list tools.

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?

Gives useful branching guidance for the list_id parameter ('with no list_id, all your lists'), which tells an agent how to choose between the two modes. It offers no when-to-use vs. alternatives or exclusions relative to sibling tools, so usage is only implied at the parameter level.

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