Skip to main content
Glama
Sign In
ontopoc

ontopoc

by Longado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_instances

Find instances of an object type by name or ID within a saved run and return matching node IDs, giving you the starting point for instance graph queries.

Instructions

按名称或编号找数据里的某个对象（实例图谱的起点），给出节点 id；对象类型没有名称字段时 name 就是识别值。

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": {
      "saved_as": "<saved_as>",
      "type": "<type>"
    },
    "name": "find_instances"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes对象的 key，来自 list_objects
queryNo名称或编号里含有的字，不分大小写；不写就列前 20 个
saved_asYes运行的保存名，来自 list_runs 或 build_ontology

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description has to carry the full behavioral burden, and it does disclose the key output (the node id) plus the identity fallback for types lacking a name field. It says nothing about how many results are returned when a query narrows things down, what happens with no match, or permissions, though it does note in both the description area and the schema that an empty query lists the first 20 results.

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?

A single front-loaded sentence that leads with the action and then adds the return value and the edge case. There is no filler, though the trailing edge-case clause is dense and would be easier to parse if it were split.

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?

For a three-parameter lookup with no output schema, it covers the essentials (what you get back is a node id) and the identity fallback. Missing is enough on result limits, empty results, and how it relates to follow-on tools like instance_neighbourhood, which matters for a tool explicitly framed as a graph entry point.

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?

The schema describes all three parameters, so the baseline is 3. The description adds only marginal meaning beyond that: it clarifies that the search key is the name or number, and it warns that for types without a name field, the name is itself the identifying value; this is useful, but most of the parameter semantics are already in 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?

States a specific verb and resource: find an object in the data by name or number, returning its node id. It also adds scope ('the starting point of the instance graph') and the fallback case for types without a name field, which helps an agent distinguish it from a plain listing. It does not name a sibling to contrast with (e.g. object_rows or instance_neighbourhood), so it falls short of 5.

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 phrase 'the starting point of the instance graph' implies this is a first step before graph traversal, but the description never gives an explicit when-to-use versus when-not or names an alternative tool. Usage is inferable, not stated.

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