ThingsPool

Face

face

Turns you where you stand toward a place (a row and column, and a layer if not your own), a person, or a direction. Your camera looks the way you face.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "face"
  }
}

Input Schema

Name	Required	Description
`row`	No
`layer`	No
`column`	No
`person`	No	A name, as look gives it.
`direction`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations declare a non-read-only, non-destructive mutation, and the description adds that the camera follows your facing, which is useful behavioral context. It does not say whether turning is instantaneous, whether it requires standing in a room, or what happens if the target is unreachable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action first and the camera consequence second. Every clause carries meaning and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description covers all five parameters and the three targeting modes, so an agent can call it without guessing. The remaining gap is that zero parameters are marked required yet the tool presumably needs at least one target, which the description does not address.

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?

With only 20% schema description coverage, the description compensates well: it explains that row/column identify a place, layer applies when the target is not on your own layer, person is a name, and direction is a compass heading. The 'or' phrasing conveys that these are alternative targeting modes, a fact the schema does not express.

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 (turn) and a clear resource (your facing/camera), and enumerates the three target modes: a coordinate place, a person, or a direction. It implicitly separates itself from look (examine) and walk_to (move), but that contrast 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 action wording ('turns you where you stand toward...'), so an agent can guess this is for reorientation without moving. There is no explicit statement of when to choose this over look or walk_to, and no prerequisites or exclusions.

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

All ThingsPool tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.