Skip to main content
Glama

Last Price

search_tools

Read-onlyIdempotent

Find the Last Price tool for a task. This connection lists only the tools that reach a price; the server has over 300 more (pricing functions, routing, experiments, webhooks, billing, orders, the marketplace and more). Pass query, a few words for the job, and get back the best matching tools with their full input schemas. Then call one with call_tool, or by its name. With no query it lists every tool name.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tools to return. Defaults to 5.
queryNoWhat you want to do, in a few words, e.g. "create a webhook" or "experiment results".

Output Schema

NameRequiredDescriptionDefault
hintNo
queryNo
toolsNo
messageNoA short sentence about the result that an agent can show its person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / message / description
      Added value: +"A short sentence about the result that an agent can show its person."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the result set includes full input schemas for the matched tools, and an empty query returns every tool name rather than an error. It notes the 300+ tool breadth of the server, which is context beyond what annotations provide.

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

Conciseness3/5

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

The core guidance is front-loaded, but the parenthetical catalog enumeration ("pricing functions, routing, experiments, webhooks, billing, orders, the marketplace and more") is padding that does not help an agent act. The opening "Find the Last Price tool" phrasing is confusing and costs the reader a pass before the real purpose lands.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description still covers the essential next step after results arrive. For a two-parameter discovery tool this is nearly complete, with only the `limit` behavior and any ordering/ranking semantics left unaddressed.

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 coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds the meaningful empty-query semantics for `query` (lists all tool names) but says nothing about `limit` beyond what the schema contains, so it adds only partial value.

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?

The description states a specific action and resource: find/list tools matching a task query, and it explicitly distinguishes itself from the rest of the catalog by noting that this connection only exposes price-reaching tools while the server hosts 300+ others. The opening phrase "Find the Last Price tool for a task" is awkward and slightly obscure, which keeps it from a 5, but the intended purpose (tool discovery) is unambiguous by the second sentence.

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?

It clearly frames the workflow: pass a few words, get matching tools with full input schemas, then invoke one via call_tool or by name. The no-query behavior is explicitly described, so an agent knows both the normal and the fallback path. It stops short of stating when not to use it (e.g., when the target tool is already known or is a visible sibling), so it is not a full 5.

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