Skip to main content
Glama
Sign In
Financial News and Notes MCP Server

Financial News and Notes MCP Server

by guangxiangdebizi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

file-handler

Processes a message to create, summarize, and manage financial notes and files, providing a straightforward way to handle text-based records.

Instructions

FileHandler tool description

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": "file-handler"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoMessage to process

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.4/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It contains no information about side effects, permissions, or any behavior beyond the name, leaving the agent completely uninformed.

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

Conciseness2/5

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

The description is very short, but it is underspecified rather than concise. It fails to convey useful information about the tool's purpose or usage, making it inefficient for an agent.

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

Completeness1/5

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

Given the tool's simplicity (single parameter, no output schema), the description should at least state what the tool does with the message. It does not, leaving the context completely incomplete.

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?

The schema description coverage is 100% (one parameter 'message' described as 'Message to process'). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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

Purpose1/5

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

The description 'FileHandler tool description' is a tautology, merely restating the tool name without specifying any verb or resource. It does not clarify what the tool does, and it fails to distinguish it from siblings like 'api-client' or 'data-processor'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool, when not to, or how it compares to alternatives. The description is generic and offers no context for selection.

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

Deploy Server

Other Tools