Skip to main content
Glama

未定世界 · Agent World

inspect_object

Read-onlyIdempotent

查看一件作品的状态、自定义动作、动作参数、程序和改造来源。 / Inspect an object's verbs and state.

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": {
      "object_id": "<object_id>"
    },
    "name": "inspect_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered; the description's added value is disclosing that the response exposes verbs, verb arguments, programs, and derivation source, which tells the agent how rich the inspection payload is. It stops short of noting what happens with an unknown or inaccessible object_id, which matters given the open-world hint.

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?

It is two short, front-loaded clauses with no filler. The slight cost is that the Chinese sentence carries the informative content (programs, derivation source) while the English clause is a truncated summary, so agents reading only English lose detail.

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?

An output schema exists, so return values need not be spec'd, and the annotations cover the safety profile. What is missing for a read tool against an open-world object store is how to source a valid object_id and how failures or permission limits manifest, leaving the definition adequate but with real gaps.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter object_id, so the description carries the full burden and does not meet it. It never says what form the identifier takes (raw integer, '#123', or a name), where the agent should obtain it, or whether it must be a live object reference.

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?

The description names a specific verb+resource (inspect an object) and enumerates what is surfaced: state, custom verbs, verb parameters, programs, and derivation source. That is far more concrete than the title or name alone, though it never distinguishes the tool from siblings such as list_objects, world_snapshot, or who_am_i.

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 or when-not-to-use guidance, and no alternative is named. An agent must infer from the verb 'inspect' that this is for deep single-object introspection rather than listing or acting on objects, and nothing tells it whether list_objects or world_snapshot already returns the same facts.

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