Skip to main content
Glama

simplefunctions

by io.github.spfunctions

update_strategy

Advanced: Update a trading strategy (stop loss, take profit, status).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesSimpleFunctions API key. Get one at https://simplefunctions.dev/dashboard/keys
statusNoNew status: active|watching|executed|cancelled|review
priorityNoNew priority
stopLossNoNew stop loss (cents)
thesisIdYesThesis ID
rationaleNoUpdated rationale
entryAboveNoNew entry above trigger (cents)
entryBelowNoNew entry below trigger (cents)
strategyIdYesStrategy ID (UUID)
takeProfitNoNew take profit (cents)
softConditionsNoUpdated soft conditions

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action and fields, without disclosing update semantics (e.g., partial update behavior, effects on omitted fields), required permissions, or return value. This is insufficient for a mutation tool.

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 concise sentence, efficiently front-loaded. The 'Advanced:' prefix is slightly unnecessary but not detrimental, so it earns a high but not perfect score.

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

Completeness2/5

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

With 11 parameters, 3 required, and no output schema, the description is too sparse. It does not explain the update semantics, what happens to omitted fields, or what the response contains, leaving significant gaps for a complex mutation tool.

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 the schema already documents all parameters. The description lists three example fields (stop loss, take profit, status), which adds marginal value beyond the schema but does not harm.

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 clearly identifies the action (update) and resource (trading strategy) and lists specific fields (stop loss, take profit, status). This distinguishes it from sibling tools like update_position and update_thesis.

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?

The verb 'update' implies modifying an existing strategy, which differentiates it from create_strategy. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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

All simplefunctions toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as multiple market query tools (scan_markets, screen_markets, get_market_detail, get_market_diff, get_market_history, inspect_ticker) and legislative tools (legislation, get_legislation, list_legislation, query_gov). Aliases like get_heartbeat_config/get_heartbeat_status and explore_public/explore_theses add further confusion. An agent would struggle to select the correct tool without deeply reading each description.

Naming Consistency3/5

Most tools follow a verb_noun pattern (get_, list_, create_, update_), but there are notable deviations: 'legislation' lacks the 'get_' prefix, 'stt' and 'tts' are acronyms, 'monitor_the_situation' is a full phrase, and 'x_account/x_news/x_volume' use a non-standard prefix. The overall style is readable, but the mixed conventions reduce predictability.

Tool Count1/5

108 tools is extreme for any server, even one covering prediction markets, trading, portfolio management, forum, skills, and speech. The massive surface area overwhelms agents and makes the server feel more like a platform than a coherent toolkit. This many tools inevitably leads to redundancy and maintenance burden.

Completeness4/5

The server covers an impressively broad domain: market data, thesis management, intents, strategies, positions, portfolio, forum, skills, legislative and economic queries, and audio/visual processing. Minor gaps exist (e.g., no delete for skills/theses, no update for some portfolio items) but core workflows are well-supported. Overall lifecycle coverage for most entities is strong.

Resources