Skip to main content
Glama

Search SIGNAL issues (public)

ic_signal_search
Read-only

Substring search across every published SIGNAL issue. Matches on issue title + dek, beat label + kicker, story headline + dek + body. Case-insensitive. Returns ranked hits with a snippet + the slug + (when matched in a story) story_id. No auth required. Args: { q: string (2-120 chars), limit?: number (max 50, default 10) }.

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": {
      "q": "<q>"
    },
    "name": "ic_signal_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesText to search issues and stories for (2-120 chars).
limitNoMost results to return (1-50).

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. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Most results to return (1-50)."
    • addedInput schema / properties / q / description
      Added value: +"Text to search issues and stories for (2-120 chars)."
  3. Changed2 schema fields changed
    • removedInput schema / properties / limit / description
      Removed value: -"Most results to return (1-50)."
    • removedInput schema / properties / q / description
      Removed value: -"Text to search issues and stories for (2-120 chars)."
  4. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Most results to return (1-50)."
    • addedInput schema / properties / q / description
      Added value: +"Text to search issues and stories for (2-120 chars)."
  5. First observed

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=false, so the safety profile is covered; the description adds genuine context on top: case-insensitive matching, which fields are searched, ranked/snippet return shape, and that no auth is needed. It does not mention result ordering signals or empty-result behavior, which keeps it below a 5.

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 what is searched, then match semantics, then return shape, then constraints — a sensible ordering with no filler. The trailing 'Args' block partly duplicates the input schema, which is the only wasted space.

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 two-parameter read-only search with an output schema and full annotation coverage, the description supplies the matchable fields, return contents, and auth status — enough to call it correctly. Minor gaps (pagination of ranked hits, ordering) are not disqualifying given the output schema exists.

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 both parameters are fully described in the schema, so the baseline is 3. The 'Args' sentence restates the same constraints (2-120 chars, max 50, default 10) without adding new meaning such as tokenization, phrase handling, or ranking behavior.

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 verb and resource: substring search across every published SIGNAL issue, with an explicit inventory of the fields matched (title/dek, beat label/kicker, story headline/dek/body). The 'search' framing distinguishes it in spirit from list/get siblings, but no sibling is named, so differentiation is left to inference.

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?

Usage is only implied by the word 'search' and the substring-matching semantics; there is no explicit statement of when to reach for this instead of ic_signal_list_issues or ic_signal_get_issue. No exclusions or prerequisites are given beyond 'no auth required'.

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.