Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

find_entities

Read-onlyIdempotent

Locate bridge nodes or elements by coordinates or properties like material, section, or span; retrieve types, weights, or supports for analysis.

Instructions

    Locate nodes/elements by coordinates or attributes (按坐标或属性定位节点/单元).

    Args:
        by: Search mode (查找方式):
            "node_at_point" (按坐标找节点, 需 x/y/z, 可选 tolerance),
            "elements_at_point" (按坐标找单元, 需 x/y/z, 可选 tolerance),
            "elements_by_material" (按材料名找单元, 需 name),
            "elements_by_section" (按截面号找单元, 需 index),
            "element_type" (查单元类型, 需 ids),
            "element_weight" (查单元重量, 需 ids),
            "span_supports" (跨径支承信息, 需 span_info_name),
            "span_elements" (跨径单元信息, 需 span_info_name)
        x, y, z: Coordinates for point search (坐标)
        tolerance: Search tolerance (容差)
        name: Material name (材料名)
        index: Section ID (截面号)
        ids: Element IDs (单元编号)
        span_info_name: Span info name (跨径信息名)
        limit: Max items per page (单页条数上限)
        offset: Pagination offset (翻页偏移)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
zNo
byYes
idsNo
nameNo
indexNo
limitNo
offsetNo
toleranceNo
span_info_nameNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds the pagination parameters and mode-dependent search behavior, but doesn't disclose return format or edge-case behavior. It is consistent with annotations, neither contradicting nor significantly expanding them.

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?

The description is long, but the structured list of modes and parameters is information-dense and every line corresponds to a decision an agent must make. It leads with the primary purpose and then details the branching modes efficiently. The dual-language repetition adds length without much extra semantic value, but doesn't obscure the content.

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?

Given there is no output schema, the description should clarify what the tool returns (e.g., entity IDs, coordinates, count) and any default behavior when no entities match. It provides complete input-side guidance but is silent on output structure and failure semantics. This is the main completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has zero description coverage, so the description carries full burden. It explains every parameter, including conditional requirements (e.g., x/y/z needed for point searches, name for material, index for section) and the role of limit/offset. This is a thorough compensating explanation.

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?

Description states the tool locates nodes/elements by coordinates or attributes, with a verb ('Locate') and resource. It enumerates eight distinct search modes, making its scope concrete and distinguishing it from other query tools like get_model_info or display_ids.

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?

The Args list maps each 'by' mode to the required parameters, giving an agent an explicit decision procedure for selecting a mode. It doesn't name sibling alternatives or state when not to use find_entities, but the mode breakdown provides clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SorataYang/qiao-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server