Skip to main content
Glama
Sign In
omiss-mcp

omiss-mcp

by qso-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Omiss Award Recipients

omiss_award_recipients
Read-onlyIdempotent

List OMISS award recipients newest-first, or filter certificates by callsign or member number to verify whether a specific station holds an award.

Instructions

List who holds an OMISS award, newest certificates first, or check one member.

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": {
      "award_id": "<award_id>"
    },
    "name": "omiss_award_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many (default 100).
award_idYesThe award's ID, from omiss_awards (e.g. ALPHABETSOUP).
callsignNoOnly this station's certificates.
om_numberNoOnly this member's certificates.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to repeat safety properties. It adds useful context about certificate ordering and member filtering, but says nothing about pagination or the default limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single efficient sentence with no wasted words. The primary listing purpose is front-loaded, and the alternate 'check one member' mode follows naturally.

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?

With annotations covering safety, a 100% documented schema, and an output schema, the description is nearly sufficient for correct invocation. The only minor gap is that it does not mention the limit/pagination aspect, though the schema does document that parameter.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description slightly reinforces award and member filtering but adds no new syntax, default, or constraint details beyond the schema.

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 ('List') and resource ('who holds an OMISS award'), plus an alternate mode ('check one member'). It is clearly distinct from the sibling omiss_awards, which appears to list the awards themselves, but it does not explicitly name that sibling.

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?

The phrase 'or check one member' implies that callsign/om_number filters can narrow results, and 'newest certificates first' gives ordering context. However, it does not explicitly say when to use this tool versus omiss_awards, omiss_member_lookup, or omiss_award_rules.

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

Deploy Server

Other Tools