Skip to main content
Glama

search_endpoint

[Personal research only] Searches for stock symbols and company names based on keywords (e.g., 'Tesla', 'Microsoft Corp').

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": {
      "keywords": "<keywords>"
    },
    "name": "search_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to search for company names or stock symbols (e.g., 'Tesla', 'Microsoft Corp', 'AAPL')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It implies a read-only lookup, but says nothing about matching semantics (partial prefix vs exact), result limits, whether exchange/asset-type is returned, or how ambiguous multi-match queries behave — all material for a search tool. The '[Personal research only]' tag hints at a usage constraint but is not explained.

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 short, front-loaded sentence with no filler. The bracketed disclaimers at the very front are slightly cryptic and occupy the highest-attention slot, which costs a point.

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

Completeness3/5

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

For a one-parameter, annotation-free tool with no output schema, the description covers the basic action but leaves return shape (list of symbols? company names? exchange metadata?) and ambiguity behavior unexplained. Minimum viable, with a real gap around what the agent gets back.

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 description coverage is 100%, and the single keywords parameter is already documented with the same examples ('Tesla', 'Microsoft Corp') the description uses. The description therefore restates schema content rather than adding format, matching, or tolerance details, which sets the baseline at 3.

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?

Names a specific verb (searches) and target (stock symbols and company names) with an example keyword family, which is enough for an agent to tell it apart from data-fetching siblings like fetch_quote or fetch_company_overview. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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 when-to-use guidance: nothing says this is the symbol-resolution step that should precede fetch_quote or analyze_stock, nor any exclusion conditions. The only guidance-like phrase is the bracketed '[Personal research only]' tag, which reads as an access restriction rather than an instruction on tool selection.

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