Skip to main content
Glama

IKANGAI Vibe Support

List safety notices

list_notices
Read-only

List the safety and upkeep notices: title, topic, who each one is for, a summary and its id. Pass the tool the person builds with to get only what applies to it. Use this before work on login, payments, personal data or deleting data, and when asked what to check before going live. Call get_notice with an id for the checklist, the steps and the messages to paste.

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

Input Schema

NameRequiredDescriptionDefault
toolNoOnly what applies to this tool. Leave out for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavior: what fields come back, that passing a tool narrows results to what applies, and that per-notice detail lives behind get_notice. It does not mention ordering, pagination or volume, which keeps it short of 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?

Three sentences, front-loaded with what comes back, then filtering, then when to use it and where to go next. Every sentence carries information; only 'Pass the tool the person builds with' is slightly awkward phrasing.

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 no output schema, the description carries the return-shape burden and does so by naming the fields. For a one-parameter read-only listing it covers purpose, filtering, triggers and the follow-up call, leaving nothing an agent needs in order to invoke it correctly.

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 the enum and its 'leave out for everything' default are already documented. The description adds the semantic effect ('get only what applies to it'), which tells the agent the filter is a relevance narrowing rather than an exact-match lookup — meaning beyond the schema.

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?

Specific verb plus resource ('List the safety and upkeep notices') with the returned fields enumerated (title, topic, audience, summary, id). It also distinguishes itself from the sibling get_notice, which returns the deeper detail for a single id, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Explicit triggers are named ('before work on login, payments, personal data or deleting data', 'when asked what to check before going live'), and the alternative is named with its selection condition ('Call get_notice with an id for the checklist, the steps and the messages to paste'). Nothing is left to inference.

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