Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Company watch status

get_surveillance_watch
Read-only

Retrieve the status and 100 most recent events of a surveillance watchlist using its creation token, so you can monitor company-registry changes and review recent activity.

Instructions

Status and the 100 most recent events (total and cut in listes_bornees.evenements) of a watchlist created with create_surveillance_watch; event types and payloads in listes_fermees.type_evenement_surveillance of GET /v1/lecture. Free: the surveillance_id token IS the capability.

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": {
      "surveillance_id": "<surveillance_id>"
    },
    "name": "get_surveillance_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
surveillance_idYesToken returned at creation

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context beyond them: results are capped at the 100 most recent events, with the true total surfaced separately, and the event taxonomy lives in a separate reference endpoint. The line 'the surveillance_id token IS the capability' discloses the auth model (no further credentials needed) and that the call is free, which is exactly the kind of fact annotations cannot carry.

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?

Two compact clauses with the resource and cap stated first and supporting references after; no filler sentences. The density comes at some cost to readability because it cites internal field paths and an endpoint path rather than plain language.

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?

An output schema exists, so return-value shape need not be explained. Given a one-parameter read tool, the description covers the cap, the count semantics, the event-type reference, and the auth/billing model, leaving little that an agent would need before calling it.

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% and the single parameter is already documented as the token returned at creation. The description reinforces that the token doubles as the capability and is free, but adds no format, lifetime, or error semantics beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (the status of a watchlist) plus the payload returned (status plus the 100 most recent events), and anchors it to create_surveillance_watch, which separates it from the create/renew/stop siblings. The raw field-path jargon (listes_bornees.evenements) is opaque unless the agent already knows the response envelope, which slightly blunts the clarity.

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

Usage Guidelines3/5

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

Implied usage is clear enough: call it to read the state of a watch that was previously created with create_surveillance_watch. There is no explicit when-not guidance and no mention of what happens if the watch has expired or been stopped, so the agent must infer the boundary conditions.

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