Skip to main content
Glama
Sign In
SimpleFunctions

SimpleFunctions

by spfunctions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fork_thesis

Clone any public thesis into your account to inherit its causal tree as a starting point for iteration. Use to build upon existing analysis instead of creating from scratch.

Instructions

Clone a public thesis (by id or slug) into the authenticated user's account, copying its causal tree as a starting point. Side-effectful. Requires SF API key. Use when you want to iterate on someone else's thesis; use create_thesis to start from scratch.

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": {
      "apiKey": "<apiKey>",
      "idOrSlug": "<idOrSlug>"
    },
    "name": "fork_thesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYesSF API key (sf_live_...). Required.
idOrSlugYesSource thesis ID (uuid) or public slug. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / apiKey / description
      Added value: +"SF API key (sf_live_...). Required."
    • changedInput schema / properties / idOrSlug / description
      Previous value: -"Thesis ID or public slug"New value: +"Source thesis ID (uuid) or public slug. Required."
    • addedInput schema / properties / idOrSlug / minLength
      Added value: +1
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Clearly labels as 'Side-effectful' and requires API key. Could add details like whether original is modified, but 'clone' implies no modification.

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 sentences with no wasted words, front-loaded with main action. Highly concise and well-structured.

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 simple two-parameter tool with no output schema, description covers purpose, guidelines, and side-effects adequately. Could mention privacy of copied thesis but not essential.

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 coverage is 100%, so baseline 3. Description restates schema info but adds no extra semantics beyond what's already in the input schema.

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 states 'Clone a public thesis' with specific verb and resource, and distinguishes from sibling by referencing 'create_thesis' for starting from scratch.

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?

Explicitly states when to use ('iterate on someone else's thesis') and when not ('use create_thesis to start from scratch'), plus mentions API key requirement.

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

Deploy Server

Other Tools