Skip to main content
Glama

Search scored FTSE 100 news

search_news
Read-onlyIdempotent

Search every FTSE 100 story or headline MarketFrame has scored.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
pageNo
sortNo
toneNo
typeNo
queryNo
companyNoCompany slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds only that results are restricted to content MarketFrame has already scored, which is mild scope context. It does not disclose pagination behavior, default sort order, or result limits, which matter for an 8-parameter search tool.

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?

A single short sentence with the resource and scope front-loaded and no filler. It is efficient, though the brevity is partly a symptom of under-specification rather than disciplined editing.

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

Completeness2/5

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

For a tool with eight optional parameters, no required fields, three enums, low schema coverage, and no output schema, one sentence is not enough. The agent lacks date-range semantics, pagination behavior, sort default, and how tone/type filters interact with the query. Annotations cover safety, but the operational picture is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% (only 'company' has a description), so the description is expected to compensate, and it does not. None of the eight parameters (from/to date, page, sort, tone, type, query, company) are explained, aside from a faint hint that both 'stories' and 'headlines' exist as result types. An agent must reverse-engineer date formats, pagination, and sort semantics from names alone.

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 ('Search') and resource ('every FTSE 100 story or headline MarketFrame has scored'), which is clearer than a bare title restatement. It implies a coverage scope (only scored content) but does not distinguish itself explicitly from the retrieval siblings like get_story or get_company, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to choose search_news over get_story, get_company, or get_ftse100_today, no prerequisites, and no mention of what to do when no results are scored. The use case is only inferable from the verb 'Search' and the 'FTSE 100' scope.

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