Skip to main content
Glama

SMIFS Limited

Search SMIFS research

search_research
Read-onlyIdempotent

Search SMIFS research and market-commentary posts by title (case-insensitive), newest first, or list the latest posts when no query is given. Returns title, publish date, URL and a short summary. Research is general information, not personalised investment advice.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many posts to return (1-25).
queryNoWords to match in post titles. Omit for the latest posts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: result ordering (newest first), the matched field (titles, case-insensitive), the returned fields, and a compliance note that the content is general information rather than personalised advice. Pagination/rate-limit behavior is not described, keeping it below 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 compact sentences plus a short disclaimer, all front-loaded: capability and fallback first, return fields second, compliance note last. No redundant wording.

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

Completeness5/5

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

Although there is no output schema, the description enumerates the returned fields (title, publish date, URL, short summary), the ordering, and the no-query behavior. For a two-optional-parameter read tool, nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the case-insensitivity of the query match and the newest-first ordering that the schema does not state. The limit parameter is only indirectly implied ('latest posts'), which keeps it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (SMIFS research and market-commentary posts), plus the exact match target (titles, case-insensitive) and the no-query fallback (list latest). This is clearly distinct from the sibling tools, which cover accounts, company profiles and products.

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

Usage Guidelines4/5

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

Explicitly tells the agent to omit the query to get the latest posts, and implicitly covers the search case when a query is given. There is no explicit 'when not to use' or named alternative, but the siblings do not overlap in purpose, so the guidance is sufficient.

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