Skip to main content
Glama
Sign In
SimpleFunctions

SimpleFunctions

by spfunctions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_context

Obtain a global market snapshot with top mispriced edges and 24h price movers, or retrieve a thesis-specific context bundle including causal tree, signal log, and evaluation history. Use as the starting point before calling other tools.

Instructions

START HERE — single entry point that returns either a global market snapshot or a thesis-specific context bundle. Global mode (no args): top mispriced edges, 24h price movers, highlights, traditional markets. Thesis mode (thesisId + apiKey): adds causal tree, signal log, and evaluation history for that thesis. Read-only, no rate limit. Use this first; only call get_edges / get_changes / get_world_state if you need that single slice in isolation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
thesisIdNoThesis ID (uuid or slug). Omit for global snapshot. If set, apiKey is required.
apiKeyNoSF API key (sf_live_...). Required when thesisId is set; ignored otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / apiKey / description
      Previous value: -"SF API key. Required for thesis-specific context."New value: +"SF API key (sf_live_...). Required when thesisId is set; ignored otherwise."
    • changedInput schema / properties / thesisId / description
      Previous value: -"Thesis ID. Omit for global market snapshot."New value: +"Thesis ID (uuid or slug). Omit for global snapshot. If set, apiKey is required."
  2. First observedv0.1.1

TDQS

A5/5.0
Behavior5/5

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

Discloses read-only nature and no rate limit, beyond basic annotations (which are absent). Describes output content for both modes, providing behavioral context.

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?

Front-loaded with purpose, 4 sentences with zero waste. Every sentence adds essential information without redundancy.

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

Completeness5/5

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

For a 2-param tool with no output schema, description covers return content for both modes, usage order, and sibling tool differentiation. Fully sufficient for agent context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by explaining the role of each parameter: omitting thesisId yields global snapshot, setting it requires apiKey. Clarifies conditional logic.

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?

Description clearly states it's a single entry point returning either a global snapshot or thesis-specific bundle. Uses explicit 'START HERE' and differentiates modes, distinguishing from siblings like get_edges.

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 says 'Use this first; only call get_edges / get_changes / get_world_state if you need that single slice in isolation.' Provides clear guidance on when to use and when not to, with alternatives named.

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