Skip to main content
Glama

Record a spark's outcome

update_spark

Record outcome and status of a spark action, including cost and value, to build a reward history for learning when to surface problems. Log failures too.

Instructions

Record what happened when you acted on a spark — an outcome note, a new status (tried / worked / failed), and ideally the cost (effort spent) and value (graded payoff). LOG FAILURES TOO: 'most bets fail' is the premise of problem #2, so failed and zero-value outcomes are exactly the signal a spend-policy is learned from — recording only wins makes the history unusable. This outcome history is what lets the system learn when surfacing a dormant problem is worth the attention.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpark id
costNoACTUAL effort spent chasing it to a verdict (same scale as capture's cost).
valueNoGraded payoff of the outcome: 0 if it failed or yielded nothing, higher for bigger wins (heavy-tailed). The reward signal the budget policy is fit on — log it for failures too.
statusNoNew status for the spark
outcomeNoWhat happened when you tried it
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains the meaning of cost, value, and status fields, and stresses that value should be 0 for failures. It does not mention side effects or auth needs, but the behavioral context is well-addressed.

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 focused paragraph of about 4-5 sentences, front-loading the main purpose then emphasizing failure logging. Each sentence adds value; no wasted words.

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 5-parameter tool with no output schema, the description covers purpose, usage guidelines, and parameter semantics well. It lacks return value info but that is not critical here. Completeness is high.

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%, but the description adds significant meaning: clarifies cost as 'ACTUAL effort spent', value as 'graded payoff' (0 for failures), and explains the importance of recording failures. This goes beyond 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 title 'Record a spark's outcome' and description clearly state the tool's purpose with specific verb and resource. It distinguishes from siblings like capture_spark (new spark capture) and evoke (retrieval) by focusing on outcome recording.

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 explicitly guides when to use the tool: after acting on a spark. It strongly emphasizes logging failures, providing rationale ('most bets fail'). No explicit alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pierreb4/seven-dpt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server