Skip to main content
Glama

Get the latest SIGNAL issue summary (public)

ic_signal_get_latest
Read-only

Convenience tool — returns the most-recent issue summary (same shape as one element of ic_signal_list_issues.issues[]). No auth required. Args: { include_stories?: boolean (default false — when true the issue's story list is inlined as stories[] with id/title/dek, saving a follow-up ic_signal_get_issue round trip) }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ic_signal_get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_storiesNotrue inlines the issue's stories (id, title, dek). Default false.

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_stories / description
      Added value: +"true inlines the issue's stories (id, title, dek). Default false."
  3. Changed1 schema field changed
    • removedInput schema / properties / include_stories / description
      Removed value: -"true inlines the issue's stories (id, title, dek). Default false."
  4. Changed1 schema field changed
    • addedInput schema / properties / include_stories / description
      Added value: +"true inlines the issue's stories (id, title, dek). Default false."
  5. Changed1 schema field changed
    • addedInput schema / properties / include_stories
      Added value: +{
      +  "type": "boolean"
      +}
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds what they do not: no auth required, and the concrete effect of the optional flag on the payload. It does not discuss pagination or failure behavior if no issue exists, which is the only remaining gap.

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 purpose, then auth, then the single argument — a sensible order. It is dense with parentheticals, but nearly every clause carries new information; only the leading 'Convenience tool —' label is mildly redundant with the rest.

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?

With one optional boolean, an output schema present, and annotations carrying the safety profile, the description covers everything an agent needs: what it returns, its relationship to sibling shapes, auth requirements, and the one parameter's tradeoff. Nothing material is missing.

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%, so baseline is 3; the description goes beyond it by stating the default (false), the exact inlined fields (id/title/dek), and the practical motivation (avoiding a follow-up get_issue call). That is meaning the schema text alone does not convey.

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 and resource ('returns the most-recent issue summary') and pins the return shape relative to a sibling ('same shape as one element of ic_signal_list_issues.issues[]'). An agent can distinguish this from ic_signal_get_issue and ic_signal_list_issues 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?

Frames the tool as a convenience shortcut and explains the tradeoff against the alternative: include_stories=true saves a follow-up ic_signal_get_issue round trip. It gives clear context for when to use it, but stops short of explicit exclusions (e.g., when the latest issue is not the one you want, use list_issues).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.