Skip to main content
Glama

AIgorithmic Butterfly Effect

Look at one thing

look
Read-only

Look closely at one item by id: a line (s013, w000042), a picture (m00123), a recording (r026), one minute of a recording (r026.0431), a theme (t-snow) or a person (p-name). Returns its words, what answers it, and links to the picture or frame.

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": {
      "id": "<id>"
    },
    "name": "look"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
open_sensitiveNoSet true only if you have decided to open material marked sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main contribution is the return shape: 'its words, what answers it, and links to the picture or frame.' It says nothing about what sensitive material looks like when returned, or what changes if open_sensitive is left false, which is the one behavior an agent would want disclosed for a read tool with that flag.

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?

One sentence, front-loaded with the action and scope before the example list, and the examples are the kind of concrete data an agent needs to form a valid id. The parenthetical enumeration is dense but not padded, though it could be broken out for faster scanning.

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?

With no output schema, the description does cover the return contents in one clause, which is the key completeness need. However, for a tool that exposes an open_sensitive switch, it never explains the consequence of that switch — what a sensitive result looks like or how the agent should decide — leaving a real behavioral hole in an otherwise tight definition.

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

Parameters4/5

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

Schema coverage is only 50% and the id property has no schema description at all, so the description carries the burden — which it does well by spelling out the accepted id formats and giving a literal example for every type. The open_sensitive parameter is left entirely to the schema's own text, so it adds nothing on that half.

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 concrete verb and scope ('Look closely at one item by id') and then enumerates the exact id types accepted (line s013/w000042, picture m00123, recording r026, minute r026.0431, theme t-snow, person p-name). This makes the resource unambiguous, but it never explicitly positions itself against siblings like listen or say, so differentiation is inferred rather than stated.

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?

Usage is implied by the id-prefix enumeration — an agent can infer this is the lookup path for a known id — but there is no stated when-to-use/when-not guidance and no pointer to an alternative tool for different intents. The reader must connect the prefixes to their own task themselves.

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.