Skip to main content
Glama
Sign In
@sgs/oa-mcp-server

@sgs/oa-mcp-server

by lipeng5941
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

查询会议室

search_room

Search for meeting rooms by name, minimum capacity, or building. Paginate through results to find a room that fits your needs.

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": "search_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo每页条数
roomnmNo会议室名称
currentNo页码
buildingNo楼宇
capacityNo最低容纳人数

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It identifies the operation as a query ('查询'), implying a safe read-only action, and lists filterable fields. However, it does not disclose pagination behavior, default result size, or any other behavioral traits beyond the basic query nature.

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 (two in Chinese) that efficiently conveys the core purpose and main filters. There is no wasted wording, and it is front-loaded with the main action.

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?

For a simple query tool with 5 parameters and no output schema, the description plus 100% schema coverage is mostly sufficient. It clearly indicates a list result and the main filter criteria, though it omits mention of pagination parameters (current/size) which are present in the schema. This is a minor gap given the low complexity.

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 the baseline is 3. The description merely restates some parameter purposes (name, capacity, building) without adding new semantic meaning or clarifying nuances like 'capacity' meaning minimum capacity. No value is added 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?

The description clearly states '查询会议室列表' (query meeting room list), specifying the verb and resource. It also mentions filters, which distinguishes it as a list/search operation from detail retrieval. However, it does not explicitly name or contrast sibling tools like get_room_detail.

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 meeting rooms with filters, but provides no explicit guidance on when to use this tool versus alternatives like search_office or get_room_detail. The context is clear but lacks exclusions or alternative references.

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