Skip to main content
Glama
Sign In

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by biz.valuein
OverviewDiscussionsAdmin

Delete Signal

delete_signal
DestructiveIdempotent

Soft-delete a signal by its id (from create_signal/list_signals): status flips to deleted and it is removed from the cron evaluator index so it stops firing. Signals are immutable — to change one, delete then create_signal. Idempotent. Tier: sp500+ (sample rejected).

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": {
      "signal_id": "<signal_id>"
    },
    "name": "delete_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
signal_idYesIdentifier of the signal to soft-delete, as returned by create_signal or list_signals.

Output Schema

NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
statusYes
signal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / _meta / properties / price_as_of
      Removed value: -{
-  "description": "ISO timestamp when the price surfaces were last refreshed.",
-  "type": "string"
-}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say destructive/idempotent; the description goes well beyond by clarifying this is a SOFT delete (status flip, record retained), that it has a side effect on the cron evaluator index so the signal stops firing, that signals are immutable, and that a tier is required. The only redundancy is restating 'Idempotent', which the annotations already declare.

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?

Front-loaded with the effect and side effect, and each clause carries information (soft-delete, index removal, immutability workaround, idempotency, tier). The telegraphic 'Tier: sp500+ (sample rejected)' is compact but slightly opaque shorthand.

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 one-parameter mutation with an output schema and full annotation coverage, nothing material is missing: side effects, reversibility semantics, prerequisites, and the practical alternative are all covered.

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% for the single signal_id parameter, so the schema already carries the meaning and format. The description adds only the provenance hint (id from create_signal/list_signals), so the baseline 3 applies.

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?

States a specific verb+resource ('Soft-delete a signal by its id') plus the exact effect: status flips to `deleted` and it is dropped from the cron evaluator index. An agent can distinguish this from create_signal, list_signals, and the other delete_* tools without opening a schema.

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?

Gives clear routing: id must come from create_signal/list_signals, and to change a signal you delete then re-create rather than editing. It also states an eligibility gate ('Tier: sp500+ (sample rejected)'), which tells the agent when the call will fail. It stops short of an explicit when-not-to-use statement, so it is not a full 5.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources