Skip to main content
Glama

Name people and agents

actors_resolve
Read-only

Name the people, agents and organizations behind the ids that wiki history, logs, notes, records and grants carry. Returns name, avatar, whether each person is in the caller's organization, and organization names; null for ids the caller has not seen.

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": {
      "ids": "<ids>"
    },
    "name": "actors_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesUser or agent ids, e.g. actor.id and actor.onBehalfOf from wiki_history.
orgsNoOrganization ids, e.g. actor.org, present when an author acted from another organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by stating that unseen ids return null, which warns the agent that a missing name is a visibility artifact, not an error. It does not discuss batching behavior, partial results, or ordering for a 100-id batch, so it stays at a solid but not exceptional level.

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 sentences, front-loaded with the purpose and followed by the return shape. Every clause earns its place — the source enumeration scopes the tool and the return/null sentence tells the agent what to expect back. No filler or redundant restatement of the title.

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

Completeness5/5

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

With only two parameters, full schema coverage and read-only annotations, the remaining burden is describing the response, which it does (name, avatar, org membership, org names, null semantics). Since no output schema exists, that return description is necessary and present, leaving no significant gap for a tool of this complexity.

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?

Schema description coverage is 100%, and the schema already supplies id formats, maxItems and the example 'actor.id and actor.onBehalfOf from wiki_history'. The description adds only thematic framing about which subsystems produce such ids, so the baseline of 3 applies with no meaningful gain over the structured fields.

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?

The description opens with a specific verb-and-resource pair ('Name the people, agents and organizations behind the ids') and enumerates the exact sources those ids come from — wiki history, logs, notes, records and grants. That scoping makes it unmistakable against siblings like wiki_resolveNote or wiki_history, which deal with note or change content rather than identity resolution.

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?

It gives clear positive guidance: use this when you have ids harvested from history, logs, notes, records or grants and need human-readable identity. That covers the dominant call path, but it offers no explicit exclusions or pointers to an alternative for resolving a note or page rather than an actor.

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