Skip to main content
Glama

找接口 / Find an endpoint

find
Read-only

按自然语言找合适的数据接口,返回接口 ID、说明和每次价格。免费。Find endpoints for what the user wants, with their IDs and prices. Free.

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": {
      "query": "<query>"
    },
    "name": "find"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes用户想要的数据,例如「TikTok 视频评论」「小红书笔记评论」「X 趋势」/ What the user wants, e.g. "tiktok comments", "youtube channel subscribers"
platformNo只在这个平台里找(可选)/ Limit to one platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With readOnlyHint=true and openWorldHint=false already supplied, the safety profile is covered by annotations. The description adds genuine value by disclosing the return fields (endpoint ID, description, per-call price) and that the search itself is free — useful for cost-aware planning. It stops short of saying how results are ranked or how many come back.

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?

Purpose is front-loaded in the first clause and the whole definition is two short sentences per language. The Chinese and English halves are near-verbatim duplicates, which is reasonable for a bilingual audience but adds no new information.

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, and the description does compensate by naming the returned fields and the pricing model, which is the key missing piece. However, it omits result-count/ranking behavior and the handoff to the execution step, which matter for a two-parameter discovery tool in a paid-endpoint catalog.

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%, with both query and platform documented and an enum for platform, so the baseline is 3. The description only echoes that the query is natural language, adding nothing about query phrasing or how the optional platform filter interacts with results.

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?

States a specific verb and resource ("Find endpoints for what the user wants") plus the return payload (ID, description, per-call price), so the agent knows this is a discovery/search tool rather than an executor. It does not contrast itself with the siblings (account, call, describe), leaving the find-vs-describe distinction implicit.

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?

There is no explicit when-to-use statement, no exclusions, and no named alternative. The agent must infer that this is the first step before calling an endpoint, and nothing tells it whether to use this instead of "describe" when it already knows an endpoint.

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