Skip to main content
Glama
mcp-toolkit

mcp-toolkit

by Dongnb66

travel_hotspot_rank

Ranks travel locations by a weighted heat score from post count, votes, and ratings, and aggregates frequent advantages from user posts.

Instructions

地点口碑榜聚合:输入地点列表与用户帖子,按「发帖数2 + 投票3 + 平均评分*5」计算热度并排序,同时聚合每地点的高频优点。算法源自 travel-rank 项目,面试可两边对拍。

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": {
      "locations": "<locations>",
      "posts": "<posts>"
    },
    "name": "travel_hotspot_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsYes帖子列表(含投票、评分、优点标签)
locationsYes地点列表

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, but it does disclose the actual scoring weights and that results are sorted, which is real behavioral value an agent cannot get from the schema. It stays silent on side effects, whether locations with zero posts are dropped, tie-breaking, and how many advantage tags are kept.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The formula is front-loaded and dense in a good way, but the trailing clause about the travel-rank project and 'cross-checking on both sides in an interview' is meta-commentary that consumes space without helping an agent call the tool.

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?

There is no output schema, yet the description never sketches the return shape — presumably a ranked list with a heat score and aggregated advantages per location. For a two-array aggregation tool the scoring logic is well covered, but the result format and edge-case handling are left to inference.

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%, so the two top-level arrays are already documented, establishing a baseline of 3. The description adds a little by tying posts' votes and ratings to the scoring formula, but says nothing about how fields like pinned, category, or createdAt influence ranking.

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?

Names a concrete verb and resource: aggregates a location list plus user posts, computes a heat score and sorts, and separately aggregates per-location advantage tags. The exact weighting formula (posts*2 + votes*3 + avg rating*5) leaves no ambiguity about what the tool produces, and no sibling operates on this data.

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?

The description never says when to reach for this tool versus doing something else, nor any precondition such as requiring posts to already be fetched. Usage is only inferable from the stated purpose, and no exclusions or alternatives are mentioned.

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