Skip to main content
Glama

Maplith

by com.maplith
OverviewDiscussionsAdmin

list_signals

Read-only

What has changed on this map, as typed events with a severity, the objects they concern and a payload of counts and structure. This is the pulse: poll it to find work rather than re-reading the whole map — a finding that appeared or went away, a finding whose status a human moved, a process step that now takes twice as long, a process that stopped running altogether. Filter with since (an ISO timestamp from a previous call), kinds and unacted; page with limit and the returned next_cursor. Payloads carry aggregates and structure, not rows. Follow a signal up with list_findings for its finding_key, or get_object and route for the objects it names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindsNo
limitNoSignals per page, 1-100. Default 50.
sinceNoISO 8601 timestamp — only signals created after it.
cursorNoThe next_cursor from the previous call.
unactedNoOnly signals nobody has recorded an action against yet. For a key limited to part of the map, a record counts only when that key may see it: one made without the signal's current version, or while the signal named objects outside the key, does not, so such a signal still comes back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / unacted / description
      Previous value: -"Only signals nobody has recorded an action against yet."New value: +"Only signals nobody has recorded an action against yet. For a key limited to part of the map, a record counts only when that key may see it: one made without the signal's current version, or while the signal named objects outside the key, does not, so such a signal still comes back."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the operation as read-only, and the description adds useful behavioral context: signals are typed events with severity, payloads are aggregates rather than rows, and pagination uses a returned next_cursor. It also hints at polling semantics, which is valuable beyond the readOnlyHint.

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 concise yet information-dense, front-loading the core concept, then giving examples, filters, pagination, payload semantics, and follow-up tools. Every sentence earns its place, with no redundant restating of the title or schema.

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 tool with five optional parameters and no output schema, the description covers the signal shape, filtering options, pagination, payload nature, and follow-up routes. It does not detail the exact return fields or severity values, but the description is complete enough for an agent to invoke the tool correctly.

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 80% with detailed descriptions for limit, since, cursor, and unacted. The description adds some context, such as since being 'an ISO timestamp from a previous call' and using 'the returned next_cursor,' but it does not substantially expand on the kinds parameter or the exact filtering semantics beyond what the schema already provides.

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 clearly identifies the resource as 'signals' and the operation as polling ('poll it to find work'), framing it as a list of map changes. It distinguishes the tool from siblings by positioning it as the 'pulse' versus re-reading the whole map, and by routing follow-ups to list_findings, get_object, and route.

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?

It gives clear when-to-use guidance: poll this tool to discover changed work rather than re-reading the entire map. It also explains follow-up usage with list_findings, get_object, and route, though it does not explicitly enumerate when NOT to use this tool or name a direct alternative.

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

All Maplith 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