Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Follow a stock, asset or calendar item (the first follow in a sector creates an

sectors_follow

Follow a stock, asset or calendar item (the first follow in a sector creates an email subscription) (needs the starter plan or above)

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": {
      "sector": "<sector>"
    },
    "name": "sectors_follow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNotype=calendar: calendar item id
slugNotype=asset
typeNostock | asset | calendar
sectorYesSector slug
tickerNotype=stock
timezoneNoIANA zone for a subscription created by this call (optional)
idempotency_keyNoOptional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice
reminder_offsetsNoDays before, 0-30, up to 5 (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice",
+  "maxLength": 128,
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world mutation with idempotentHint=false. The description adds behavior beyond that: following can trigger an email subscription on the first follow in a sector, and a paid plan is required. It does not discuss retry semantics, though the schema's idempotency_key covers that.

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 description is a single front-loaded sentence with no filler, though the stacked parentheticals make it slightly awkward and the title itself appears truncated mid-phrase. It still conveys the purpose and two key constraints efficiently.

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 an 8-parameter mutation with full schema coverage and no output schema, the description covers the essential behavioral context: what is created and the plan prerequisite. It could say more about duplicate follows or what the follow record contains, but it is sufficient to call 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 every parameter is already documented, including type-specific fields like ticker, slug, and id. The description's mention of stock, asset, and calendar item types adds context for those variants but does not go beyond the schema in any material way, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource set ('Follow a stock, asset or calendar item') and notes the sector-level side effect, so an agent can distinguish it from list/unfollow siblings such as sectors_follows or sectors_unfollow. It does not explicitly name those alternatives, but the action is unambiguous.

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?

It provides a meaningful prerequisite ('needs the starter plan or above') and explains that the first follow in a sector creates an email subscription, which helps an agent decide whether the call is appropriate. It gives no explicit when-not guidance or comparison to the unfollow/list alternatives, so usage is only partly specified.

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

All SimianX AI 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