Skip to main content
Glama

A company's scored news on one day

get_company_day
Read-onlyIdempotent

Every scored headline about a company on one day, each with its tone, outlet, link, the reason for its score and the story it belongs to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>",
      "day": "<day>"
    },
    "name": "get_company_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesYYYY-MM-DD
companyYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect behavior is covered structurally. The description adds genuine value beyond that by enumerating what each headline carries — tone, outlet, link, score rationale, and parent story — which is the main behavioral unknown for a retrieval tool. It stops short of describing ordering, empty-day behavior, or volume limits.

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 well-formed sentence with no filler; the scope (company, one day) is front-loaded and the return payload is listed compactly. Nothing could be removed without losing information.

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 simple two-parameter read tool with no output schema, the description does the important work of explaining what comes back, which annotations cannot supply. The remaining gap is the company identifier format, which is the one thing an agent could plausibly get wrong when invoking it.

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 only 50%: 'day' is documented as YYYY-MM-DD in the schema, but 'company' has no schema description at all. The description confirms the semantics ('about a company on one day') but does not resolve the important ambiguity of what form the company identifier takes — ticker, exact name, or alias — so it fails to fully compensate for the coverage gap. Baseline 3 applies.

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 uses a specific verb-and-resource combination ('every scored headline about a company on one day') that makes the scope of the retrieval unambiguous: one company, one day, scored headlines only. It is clear enough to separate from siblings like get_company or search_news on scope grounds, though it never names an alternative.

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?

Usage is only implied by the narrow scope — an agent can infer it is the right tool when it wants a full day's scored news for a single company rather than a broader search. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as search_news, so the routing decision is left to inference.

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