Skip to main content
Glama

simplefunctions

by io.github.spfunctions

fork_thesis

Fork a thesis. Two modes: (1) Clone — call with just idOrSlug to copy a PUBLIC thesis verbatim into your collection. (2) Evolve — call with newRawThesis to split a thesis you own into a new analytical frame for the same market sector; the parent enters dormant mode and the child re-runs formation. Use evolve when the current frame is fundamentally inadequate for what the evidence now shows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesSimpleFunctions API key. Get one at https://simplefunctions.dev/dashboard/keys
reasonNoEvolve mode: why the original frame is no longer adequate
idOrSlugYesThesis ID or public slug
newTitleNoEvolve mode: short title for the new thesis, ≤60 chars
newRawThesisNoEvolve mode: new frame in 1-3 sentences. Omit for clone mode.
inheritEdgeMarketIdsNoEvolve mode: subset of current edge marketIds to carry over. Omit to let formation rescan fresh.

Schema Changelog

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

  1. Changed5 schema fields changed
    • changedInput schema / properties / idOrSlug / description
      Previous value: -"Public thesis ID or slug to fork"New value: +"Thesis ID or public slug"
    • addedInput schema / properties / inheritEdgeMarketIds
      Added value: +{
+  "description": "Evolve mode: subset of current edge marketIds to carry over. Omit to let formation rescan fresh.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / newRawThesis
      Added value: +{
+  "description": "Evolve mode: new frame in 1-3 sentences. Omit for clone mode.",
+  "type": "string"
+}
    • addedInput schema / properties / newTitle
      Added value: +{
+  "description": "Evolve mode: short title for the new thesis, ≤60 chars",
+  "type": "string"
+}
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Evolve mode: why the original frame is no longer adequate",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals key side effects: clone copies a PUBLIC thesis verbatim into your collection; evolve splits a thesis you own, the parent enters dormant mode, and the child re-runs formation. This goes beyond simple 'fork' semantics and aids risk assessment.

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?

The description is two sentences long, front-loads the verb and resource, and uses a clear two-mode structure. Every sentence earns its place, with no redundant filler or restating of schema fields.

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 a two-mode tool with 6 parameters and no annotations or output schema, the description covers mode selection, ownership constraints, and behavioral consequences. It does not describe the return value or potential errors, which would strengthen completeness, but the core invocation knowledge is present.

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 adds meaningful mode-level semantics: calling with just idOrSlug triggers clone, while including newRawThesis triggers evolve. This explains how the parameters interact beyond their individual schema descriptions.

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 opens with the specific verb 'Fork' plus the resource 'thesis', and immediately distinguishes two clearly named modes (Clone and Evolve) with distinct outcomes. It differentiates itself from siblings like create_thesis and fork_skill by specifying public-copy and own-thesis-split semantics.

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

Usage Guidelines4/5

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

The description gives clear context for both modes: clone when copying a public thesis, evolve when restructuring your own thesis. It explicitly states 'Use evolve when the current frame is fundamentally inadequate.' It does not explicitly name alternative tools or state when not to use fork, but the mode guidance is sufficient for selection.

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