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

connpass-user-mcp-server

by yamanoku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_connpass_user_list

Retrieve Connpass user profiles, group memberships, and event participation history by providing user nicknames.

Instructions

Fetch Connpass user information

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicknameYesConnpass user ID/nickname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are present, and the description only indicates a read operation ('Fetch'). It does not disclose authentication requirements, rate limits, or output characteristics.

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 concise sentence with no unnecessary words, earning a high score for conciseness.

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

Completeness2/5

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

Despite simplicity, the description omits what the returned data represents (list of users? profiles?), and given siblings, it is ambiguous. No output schema exists to fill the gap, so more context is needed.

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 schema already provides full coverage for the single 'nickname' parameter, so the description adds no new semantic meaning. The baseline for full schema coverage is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb ('Fetch') and resource ('Connpass user information'), but it does not specify the exact scope or distinguish this from siblings like get_connpass_user_events or get_connpass_user_group_list. The name suggests a list of users, but the description says 'user information', leaving ambiguity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus the sibling tools. There are no exclusions or alternative recommendations.

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