Skip to main content
Glama
Sign In
pysince-mcp

pysince-mcp

by LNSHRIVAS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

invalidate_source

Mark all events from a source as stale to trigger stale warnings after a resource change.

Instructions

Manually mark all events from a source as stale. Used when you know a resource has changed and want to ensure stale warnings fire.

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": {
      "source_id": "<source_id>"
    },
    "name": "invalidate_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYesSource ID to invalidate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.9

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that the tool marks events as stale and triggers stale warnings, but lacks details on reversibility, permissions, or side effects.

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?

Two sentences with no redundant text. Action and use case are front-loaded, and every sentence adds value.

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 simple one-parameter tool with no output schema, the description adequately explains the purpose and effect. It could briefly mention the return value or confirmation, but completeness is high given the tool's simplicity.

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% with a single parameter 'source_id' described as 'Source ID to invalidate'. The description adds no additional parameter context beyond the schema, 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?

The description uses specific verb+resource ('mark all events from a source as stale') and differs from sibling tools like check_staleness which likely checks staleness rather than triggering it.

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?

States when to use ('when you know a resource has changed'), providing clear context. Does not explicitly state when not to use or name alternatives, but the use case is well-defined.

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