Skip to main content
Glama

IKANGAI Vibe Support

Read one notice or showcase entry in full

get_notice
Read-only

One notice or showcase entry as Markdown: whether it applies, the problem, what could happen, the steps with the messages to paste, and every source it is based on.

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": {
      "id": "<id>"
    },
    "name": "get_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id from search, list_notices or list_showcase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by enumerating the returned Markdown document's sections (applicability, problem, consequences, steps with paste-ready messages, sources), which matters because no output schema exists. It omits error behavior for an unknown id, 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?

One sentence of roughly thirty words, front-loaded with the resource and output format before the content list. The itemized list is dense but every element names a distinct returned section, so nothing is filler; only the absence of an explicit verb slightly hurts readability.

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 single-parameter read tool with complete schema coverage and clear read-only annotations, the description covers the one thing structured fields cannot: what the returned document contains. Missing only edge-case behavior such as an invalid or unknown id.

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 the single id parameter is fully documented, including where ids come from, so the description needn't carry parameter meaning. The description adds nothing about the id beyond what the schema states, so the baseline 3 applies.

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 states the resource precisely ('One notice or showcase entry') and its representation ('as Markdown'), which implies a single-entry detail read and implicitly contrasts with the plural list_showcase/list_notices siblings. It never uses an explicit verb like 'fetch' or 'read', so the action is inferred from the title rather than the description text.

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: 'One ... entry' suggests this is the detail view used after a listing or search, and the schema's id parameter ('The id from search, list_notices or list_showcase') supplies the actual workflow. The description itself states no when-to-use condition, no exclusion, and never names an alternative tool.

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