Skip to main content
Glama

Search Acubic knowledge

acubic_search_knowledge
Read-onlyIdempotent

Searches what Acubic publishes (blog, guides, methodology, FAQ, pricing) and returns passages with links to cite. Use it for how Acubic builds and backtests strategies, plan limits and the broker connections. It does not look up individual stocks (use acubic_lookup_instrument); for one term use acubic_explain.

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

Input Schema

NameRequiredDescriptionDefault
kindsNoLimit to some kinds of content.
limitNoPage size.
queryYesWhat to look for, in plain words.
cursorNoA previous next_cursor.
localeNoThe language of this conversation.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
resultsNo
truncatedNo
next_cursorNo
index_versionNoBuild date of the content index.
total_matchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful retrieval context beyond that: results are published passages carrying citable links rather than raw data. It does not discuss paging behavior, though the cursor parameter hints at it, which keeps this below a 5.

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: what it searches, what it is for, what it is not for. Purpose and scope are front-loaded and every clause carries routing or scope information.

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 six parameters, full annotations and an output schema, the description covers purpose, scope and alternatives sufficiently for correct invocation. Pagination via cursor and the concise/detailed response format are left entirely to the schema, which is acceptable but a brief note on iterating pages would have closed the remaining gap.

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 83%, so the schema already documents query, kinds, limit, cursor, locale and response_format. The description's enumeration of content types loosely maps to the kinds enum but adds no new semantics such as paging or locale behavior. Baseline 3 is appropriate when the schema carries the parameter burden.

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 what Acubic publishes") plus the content scope (blog, guides, methodology, FAQ, pricing) and the return shape ("passages with links to cite"). It also names the two siblings it is not, so an agent can distinguish it from acubic_lookup_instrument and acubic_explain without opening either schema.

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?

Gives concrete positive use cases (how Acubic builds and backtests strategies, plan limits, broker connections) and explicit exclusions with the correct alternative for each ("does not look up individual stocks (use acubic_lookup_instrument); for one term use acubic_explain"). Routing is unambiguous.

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