Skip to main content
Glama

Get the Living Radar

get_living_radar
Read-onlyIdempotent

Plain-English AI and Grok Bot updates, each tagged Try This Week, Good to Know, or Dev Noise: Skip for Now. Every card links its source. Filter by tag or by the tools the owner uses.

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": "get_living_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly this tag.
limitNoHow many to return. Default 10.
stackNoConnector ids the owner uses. Cards for other tools are left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description isn't carrying the safety burden. It still adds context the annotations lack: results arrive as cards, every card links its source, and cards are pre-tagged and written in plain English. That tells the agent what it will receive, which matters given there is no output schema.

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 sentences, front-loaded with what the tool returns, followed by the filtering options; nothing is redundant. The colon inside the tag list reads slightly awkwardly but costs no clarity.

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 small read-only feed tool with three optional, fully documented parameters and no output schema, the description supplies the essential return semantics (cards, source links, tags) and the filtering model. It omits the default page size, but that is already stated in the schema.

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 a 3 is the floor, but the description earns more by translating the enum keys into their human labels (Try This Week, Good to Know, Dev Noise: Skip for Now), which helps an agent choose a tag value, and by pairing filtering with 'the tools the owner uses' to explain the stack parameter's intent.

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?

The description names the resource and its content precisely: a feed of plain-English AI and Grok Bot updates, each carrying one of three tags. That is clearly distinct from siblings like get_skill or search_setups. It stops short of a crisp verb framing (list/retrieve), but the content shape is unambiguous.

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 implied rather than stated: read this to get AI/bot updates, and narrow with a tag or with the tools the owner uses. There is no explicit when-not or named alternative, though none of the listed siblings obviously overlaps, so the risk of mis-selection is low.

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.

Resources