Skip to main content
Glama

A company's news dashboard

get_company
Read-onlyIdempotent

A FTSE 100 company's news dashboard: latest day's tone and why, 30-day average, last 7 days vs the week before, a written overview of the last month, the stories that moved the tone, and day-by-day history.

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>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesName, ticker or slug, e.g. "Lloyds", "LLOY".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing what the response contains (including a written narrative and historical series), which matters because there is no output schema. It omits any note on payload size, latency, or what happens for a non-FTSE-100 input.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense, front-loaded sentence with no filler; the resource and its payload are established immediately. The comma-separated list is long but every element conveys a distinct returned artifact.

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 no output schema, the description correctly carries the burden of describing return contents and does so thoroughly. For a single-parameter read tool it is nearly complete, missing only edge-case handling for companies outside the index or ambiguous names.

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 100%, so the single `company` parameter is already documented with examples (name, ticker, or slug). The description adds only the constraint that the company must be in the FTSE 100, which usefully bounds valid values but does not explain disambiguation or failure behavior.

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 specific resource (an FTSE 100 company's news dashboard) and enumerates its contents — daily tone, 30-day average, week-over-week, monthly overview, driving stories, day-by-day history. That enumeration implicitly separates it from narrower siblings like get_company_day or get_weekly_note, though no sibling is named explicitly.

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: the breadth of the payload signals 'use this for a full overview rather than a single day or week', but the description never states when to prefer get_company_day, get_weekly_note, or search_news. No prerequisites or exclusions are given.

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