Skip to main content
Glama
Sign In
futurevuls-mcp

futurevuls-mcp

by keides2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

futurevuls_get_group_members

Retrieve the list of members for a specified group by providing the group ID. Supports pagination with page number and limit parameters.

Instructions

特定グループのメンバー一覧を取得

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": {
      "group_id": "<group_id>"
    },
    "name": "futurevuls_get_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesグループID
pageNoページ番号 (デフォルト: 1)
limitNo1ページあたりの件数 (デフォルト: 20, 最大: 1000)
groupNo対象グループ名 (ERMS, DBIPS, GPF等)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as pagination limits, authentication requirements, or read-only nature. The schema includes defaults for page/limit but the description adds no context.

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?

The description is a single, concise sentence with no wasted words. It is front-loaded but lacks structural elements like bullet points.

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?

No output schema and no annotations. The description is minimal for a tool with 4 parameters; it fails to explain return format, error cases, or any important behavioral context.

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 baseline is 3. The description does not add additional meaning beyond the schema's parameter descriptions.

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 '特定グループのメンバー一覧を取得' clearly states the action (get) and resource (member list of a specific group), effectively distinguishing it from sibling tools like futurevuls_get_org_members (org-level) and futurevuls_list_groups (list groups).

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 on when to use this tool versus alternatives (e.g., get_org_members, list_groups). No conditions or prerequisites mentioned.

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