Simpler.Asia

quote_search

Read-onlyIdempotent

Finds quotes whose text fields (quote number, notes) contain every word of q; rows carry total_cents (integer CENTS) and effective_status. Refuses an empty q with VALIDATION_ERROR: send the quote number, such as QUO-2026-0001, or a word from its notes.

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": {
      "q": "<q>"
    },
    "name": "quote_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search text (substring match over the entity's text properties; %/_ are literal).
`limit`	No	Page size 1-200. Omit BOTH limit and cursor for the legacy bare-array first page of 200; pass either to get { items, next_cursor, limit } instead.
`cursor`	No	Opaque page cursor — pass a previous response's next_cursor verbatim. null next_cursor means no further pages.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish the safe read/idempotent profile, and the description adds meaningful behavior on top: the match is conjunctive across words, the row payload includes total_cents (explicitly in CENTS, preventing a unit error) and effective_status, and empty q yields VALIDATION_ERROR. Pagination and ordering behavior are left to the schema.

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, zero waste, and the high-value facts (match semantics and return fields) come first with the failure mode second. Nothing is repeated from the schema or annotations verbatim.

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?

With no output schema, the description correctly shoulders the burden of naming the returned fields and their units, and it covers the key error condition. It leaves result ordering and the default-page behavior unstated, though the latter is well handled in the schema.

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%, so the schema already documents q, limit, and cursor thoroughly — including the legacy bare-array vs. {items, next_cursor} shape. The description reinforces where q matches, but 'every word of q' sits slightly at odds with the schema's 'substring match' wording, so it neither clearly compensates nor clearly adds precision. Baseline 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 and resource (finds quotes) and narrows the search surface precisely to the quote number and notes fields, with AND-semantics over multi-word queries. What it lacks is any differentiation from the adjacent quote_list/quote_read tools, which an agent must infer from the name alone.

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?

The description gives concrete input guidance (empty q is refused; send a quote number like QUO-2026-0001 or a word from the notes), which is real usage help. But it never says when to prefer this over quote_list or quote_read, so tool selection guidance is only implied by the word 'search'.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?