Skip to main content
Glama

Basis

by com.basischarts
OverviewDiscussionsAdmin

catalog_search

Read-onlyIdempotent

Search what Basis can do: indicators, formula functions, built-in strategies, the extra series available inside strategy expressions, and the drawing tools with the number of anchors each one takes. This is a catalogue of chart objects, not callable agent functions: use tools_load for function groups. Exact counts are in the system prompt catalogue. Use this before assuming something does or does not exist — and always before drawing a new type, because a drawing tool id you guessed is refused. Reuse a type already verified in this conversation. An empty query lists a kind; no kind searches them all.

Input Schema

NameRequiredDescriptionDefault
kindNoOne of indicator, formula, strategy, variable, drawing, workflow, chartType.
limitNoDefault 25, max 100.
queryNoFree text; matches name, description and category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"One of indicator, formula, strategy, variable, drawing, workflow, chartType."
    • removedInput schema / properties / kind / enum
      Removed value: -[
-  "indicator",
-  "formula",
-  "strategy",
-  "variable",
-  "drawing",
-  "workflow",
-  "chartType"
-]
  2. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "indicator",
-  "formula",
-  "strategy",
-  "variable",
-  "drawing",
-  "workflow"
-]New value: +[
+  "indicator",
+  "formula",
+  "strategy",
+  "variable",
+  "drawing",
+  "workflow",
+  "chartType"
+]
    • removedInput schema / required
      Removed value: -[
-  "kind"
-]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful operational context beyond that: guessed drawing-tool ids are refused, exact counts live in the system prompt catalogue, and reusing verified types is preferred. It does not describe return shape or pagination, which keeps it 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.

Conciseness4/5

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

The purpose is front-loaded and the sentences mostly earn their place by covering scope, exclusions, usage, and edge cases. It is slightly dense and run-on in the opening list, but not verbose for a tool with this much routing and safety guidance.

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?

Given three optional parameters, rich annotations, and no output schema, the description covers scope, alternatives, safe usage, and empty-query behavior well. It could be more explicit about the shape of returned catalogue entries, but it gives enough context for an agent to invoke the tool correctly.

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 all three parameters are already documented. The description adds some meaning with 'An empty query lists a kind; no kind searches them all,' but does not add detail about limit behavior or query matching beyond the schema. This is the expected baseline when the schema carries the parameter semantics.

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 uses a specific verb and resource: it searches the Basis catalogue for indicators, formula functions, strategies, strategy-expression series, and drawing tools. It explicitly distinguishes this from callable agent functions and points to tools_load for function groups, so an agent can differentiate it from siblings without reading schemas.

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?

It gives explicit when-to-use guidance: before assuming something exists, always before drawing a new type, and reuse a verified type instead of re-searching. It also names tools_load as the alternative for callable function groups and explains the empty-query/no-kind behavior, leaving little to inference.

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

All Basis toolsInspect
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