Skip to main content
Glama
Sign In
futurevuls-mcp

futurevuls-mcp

by keides2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

futurevuls_get_servers

Retrieve a paginated list of servers with optional filtering by role ID or group name.

Instructions

サーバ一覧を取得。ページネーションとフィルタリングに対応

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "futurevuls_get_servers"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

A3.7/5.0
Behavior3/5

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

The description indicates a read operation ('acquire'), but with no annotations provided, it fails to disclose additional behavioral traits such as authentication requirements, rate limits, or any side effects. Mentions of pagination and filtering hint at safety, but not explicitly.

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 extremely concise, consisting of one sentence with two clauses. It front-loads the main action and supporting features with zero waste.

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?

While the description covers the main purpose and features, it omits details about the output format or return fields, which is important since no output schema is provided. For a list tool, knowing what data is returned (e.g., server IDs, names, status) is crucial for agent decision-making.

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% with all parameters documented. The description adds a high-level statement about supporting pagination and filtering, which aligns with the parameters but does not add new meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 'Get server list' (サーバ一覧を取得) and mentions pagination and filtering, distinguishing it from sibling tools like futurevuls_get_group_members or futurevuls_get_groupset_servers which focus on specific group members or groupsets.

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 implies usage for listing servers with pagination and filtering, but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions.

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