Skip to main content
Glama

Search the desk's published notes

search_notes
Read-onlyIdempotent

The published notes that carry every word asked for, in their title or their text, newest first. Matching is literal and case-insensitive: nothing is stemmed, ranked or inferred, so an empty answer means the words are not in the corpus rather than that the desk has no view. Pass a slug from here to get_note for the whole note.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many notes to return.
queryYesWords every matching note has to carry, for example "carve-out" or "data centre power".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and closed-world, and the description still adds substantive behavior: literal, case-insensitive matching with no stemming or ranking, newest-first ordering, and the crucial interpretation that an empty result means the words are absent from the corpus. That empty-result semantics is exactly the kind of context annotations cannot carry.

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?

Three tight sentences, zero filler, ordered from what the tool returns to how matching works to what to do next. Even the parenthetical contrast about empty answers earns its place by preventing a misread of zero results.

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 two-parameter read tool with no output schema, the description covers matching semantics, ordering, and the handoff to get_note, which is nearly everything needed to call it correctly. It stops short of describing the returned fields or whether results beyond the limit are reachable, a minor gap given the low complexity.

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%, with both query and limit fully documented including length bounds and default. The description reinforces the AND semantics ("every word") and the searched fields, but adds no new detail about limit behavior or pagination, so the baseline of 3 applies.

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

Purpose5/5

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

The description names the resource ("published notes"), the searched fields ("in their title or their text"), the match mode, and the ordering ("newest first") in one front-loaded sentence. That is enough for an agent to separate it from list_notes (browse) and from get_note (fetch a full note by slug), which the description explicitly routes to.

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 gives a clear follow-up workflow ("Pass a slug from here to get_note for the whole note") and implies keyword-lookup usage through the literal-matching explanation. It never explicitly states when not to use it, e.g. browsing with list_notes or searching other corpora such as search_data_buyers, so a small inference is left to the agent.

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