Meridian

Search Documentation

docs_search

Read-only

Searches Meridian's public product documentation (the same knowledge base Answers uses) and returns ranked passages with path, title, URL, heading, anchor, snippet, and relevance score. Use this to ground answers about how Meridian behaves before writing code. No app_id. Docs are not app-scoped. For Shopify Admin API, GraphQL, Polaris, or theme questions, use Shopify's official developer docs instead. This tool only covers Meridian. After a hit, call docs_get with the returned path for the full page, and use features_list / events_list for the caller's live Plan Builder keys.

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": "docs_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of passages to return (1–20). Defaults to the Answers retrieval top_k.
`query`	Yes	Natural-language question or search phrase about Meridian product behaviour.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only and closed-world safety. The description adds meaningful context beyond that: the corpus is the same knowledge base Answers uses, results are ranked passages rather than pages, the scope is not app-scoped, and the limit defaults to Answers' retrieval top_k. It stops short of describing ranking or dedup behavior, but nothing critical is withheld.

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?

Front-loaded with purpose and return contents, then routing and follow-ups. Dense but every clause carries routing or scoping information; the multiple alternative-routing sentences make it slightly longer than strictly necessary.

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

Completeness5/5

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

No output schema exists, yet the description enumerates the returned fields, and for a two-parameter read-only search it covers source, scope, ranking, defaults, and follow-on calls. An agent has everything needed to invoke it correctly.

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. The description earns an extra point by explicitly stating there is no app_id and that docs are not app-scoped, which preempts the most likely parameter mistake an agent would make.

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?

States a specific verb and resource ('Searches Meridian's public product documentation') plus the return shape (ranked passages with path, title, URL, heading, anchor, snippet, relevance score), which clearly separates it from docs_get (full page fetch) and from Shopify's docs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('ground answers about how Meridian behaves before writing code'), explicit when-not (Shopify Admin API, GraphQL, Polaris, theme questions), and explicit next steps (docs_get with returned path, features_list/events_list for live Plan Builder keys).

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

All Meridian tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?