Skip to main content
Glama

Search calculators

search_calculators
Read-only

Finds Press Equals calculators for a topic. Use short keywords ("mortgage", "paint", "days between dates", "bmi"); try a synonym if nothing comes back.

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": {
      "query": "<query>"
    },
    "name": "search_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return (default 8).
queryYesKeywords for the calculation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful behavioral detail: matching is keyword-based and can return empty, with a recommended retry strategy. It says nothing about result ordering, matching fields (name vs. description), or the shape of a returned item.

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 sentences, both earning their place, with the core purpose front-loaded and the query tactic following immediately. No filler or restated title.

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?

For a simple read-only search with fully documented parameters and no output schema, the description covers purpose, query style, and empty-result handling. The remaining gap is the search-vs-list routing decision, which is the most likely place an agent picks the wrong sibling.

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 real meaning about query construction via example terms ("mortgage", "paint", "days between dates", "bmi"), showing the expected granularity. The limit parameter is left entirely to the schema.

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 and resource ("Finds Press Equals calculators") plus the scoping dimension ("for a topic"), which implicitly separates it from a plain listing. It stops short of naming list_calculators as the unfiltered alternative, so an agent must infer the boundary between search and list.

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?

Guidance is about query formulation (short keywords, concrete examples) and failure recovery ("try a synonym if nothing comes back"), which is genuinely actionable. It gives no when-to-use guidance relative to siblings such as list_calculators or get_calculator, leaving that choice to inference.

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