Skip to main content
Glama
Sign In
connpass-user-mcp-server

connpass-user-mcp-server

by yamanoku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_connpass_user_presenter_events

Retrieve all events where a Connpass user presented by providing their nickname. Use this tool to list a user's speaking engagements.

Instructions

Fetch presenter events for a specific Connpass user

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": {
      "nickname": "<nickname>"
    },
    "name": "get_connpass_user_presenter_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicknameYesConnpass user ID/nickname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. However, it only states the action 'Fetch' without mentioning side effects, rate limits, authentication requirements, or what makes an event a 'presenter event'.

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?

The description is a single sentence with no filler or redundant content. It is appropriately concise and front-loads the core purpose effectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with one parameter and no output schema, the description is minimal but lacks essential context. It does not clarify what constitutes a 'presenter event' or what the return value represents, leaving ambiguity that could confuse users.

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?

The sole parameter 'nickname' is fully described in the schema as 'Connpass user ID/nickname', achieving 100% schema coverage. The description adds no additional meaning beyond what the schema already provides.

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?

The description uses the specific verb 'Fetch' and clearly identifies the resource as 'presenter events for a specific Connpass user'. The term 'presenter' distinguishes it from the sibling get_connpass_user_events, making the purpose 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?

The description provides no explicit guidance on when to use this tool over alternatives like get_connpass_user_events or get_connpass_user_list. Usage context is only implied by the tool name itself, not elaborated in the description.

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