Skip to main content
Glama

simplefunctions

by io.github.spfunctions

create_skill

Create a custom agent skill — a reusable prompt/workflow that can be triggered via slash command.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
autoNoAuto-trigger condition
nameYesSkill name (e.g. "precheck")
tagsNoTags for discovery
apiKeyYesSimpleFunctions API key. Get one at https://simplefunctions.dev/dashboard/keys
promptYesThe full prompt/instructions for the skill
triggerYesSlash command trigger (e.g. "/precheck")
categoryNoCategory: custom, trading, research, monitoring
toolsUsedNoSimpleFunctions tools this skill uses
descriptionYesWhat this skill does
estimatedTimeNoEstimated run time

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / toolsUsed / description
      Previous value: -"SF tools this skill uses"New value: +"SimpleFunctions tools this skill uses"
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the basic create operation and does not mention potential side effects, idempotency, name uniqueness, authorization requirements, or what happens on failure. This is a significant gap 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that communicates the core purpose without waste. It is concise and well-structured.

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?

As a mutation tool with no annotations and no output schema, the description should provide more context about expected behavior, such as return values, constraints (e.g., unique skill names), and how it relates to other skill tools. The sparse description is insufficient for the tool's complexity (10 parameters, 5 required).

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 all 10 parameters are already documented with descriptions. The tool description adds no extra parameter-level meaning beyond the schema. Baseline of 3 is appropriate when the schema handles parameter documentation.

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 a specific verb+resource: 'Create a custom agent skill' and elaborates with 'reusable prompt/workflow that can be triggered via slash command.' This clearly distinguishes it from sibling skill tools like run_skill (execute), fork_skill (copy), and publish_skill (make public).

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives. It does not mention that fork_skill is for reusing existing skills or run_skill for invoking them, nor does it state any exclusions or prerequisites. The usage context is only implied by the 'Create' verb, not explicitly explained.

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