Skip to main content
Glama

query_venues

查询粗趣小程序合作场地列表。

当用户需要找场地、了解场地信息时调用此工具。

Args:
    venue_type: 场地类型,如"桌游吧"、"运动场地"、"露营基地"等。留空则不筛选。
    location: 区域,如"南山区"、"罗湖区"。留空则不筛选。
    min_capacity: 最少容纳人数,整数或数字字符串均可,如 10 或 "10"。填0则不筛选。

Returns:
    JSON 字符串,包含场地列表(名称、类型、位置、容量、价格区间、设施等)

Input Schema

NameRequiredDescriptionDefault
locationNo城市或区域名,如:深圳、南山。不传表示不限
venue_typeNo场地类型,如:桌游吧、羽毛球馆、咖啡馆、户外草坪、会议室。不传表示不限类型
min_capacityNo最少容纳人数(整数),用于过滤掉太小的场地。不传表示不限0

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / location / description
      Added value: +"城市或区域名,如:深圳、南山。不传表示不限"
    • addedInput schema / properties / min_capacity / description
      Added value: +"最少容纳人数(整数),用于过滤掉太小的场地。不传表示不限"
    • addedInput schema / properties / venue_type / description
      Added value: +"场地类型,如:桌游吧、羽毛球馆、咖啡馆、户外草坪、会议室。不传表示不限类型"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

没有 annotations,描述隐含这是只读查询,并说明返回 JSON 场地列表及包含字段。但未说明权限要求、分页、错误处理或调用限制,行为披露有限。

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?

结构清晰,先说明用途和调用时机,再列出参数与返回。Args 和 Returns 部分略冗长,但整体可读且信息有效。

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?

工具较简单,3 个可选参数,且已有 output schema,描述覆盖了用途、调用时机、参数含义和返回内容。缺少分页或权限等补充信息,但对该查询工具已基本完整。

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 描述覆盖率 100%,参数含义已由 schema 充分说明。描述补充了示例和“填 0 则不筛选”的过滤语义,但大部分信息与 schema 重复,符合基线 3。

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?

明确说明查询合作场地列表,并指出用户找场地或了解场地信息时调用;动词和资源都具体,能与兄弟工具中的活动、支付、签到等区分开。

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

Usage Guidelines4/5

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

给出了清晰的调用场景(需要找场地、了解场地信息),但没有说明何时不应使用,也没有列出替代工具或前置条件。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources