Nopaque TotalPath

List Caller Personas

listProfiles

Read-onlyIdempotent

List the caller personas (profiles) in your workspace, newest first. Every mission-test config needs one: its profileId is a profile id from this list. Each profile has an id, a name, an optional description, and items: the named voice recordings and data values the caller can use, each with its label. Items are references (an audioId, or a datasetId and itemId), never the recorded audio or the data values themselves. Takes optional limit (1 to 1000, default 50). Use when: the user is setting up or drafting a mission test and has not said which persona to use, or asks which personas exist. Show people the profile name, not the id. If there is only one profile, it is the one to use. Cross-tool: to see which persona existing tests use, use listMissionTestConfigs (filter by profileId). Profiles are workspace-scoped.

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": "listProfiles"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max profiles to return.

Output Schema

Name	Required	Description	Default
`count`	Yes
`profiles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses ordering, workspace scoping, profile fields, and the important semantic that items are references rather than audio or data values. This is substantial behavioral context for a list tool.

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?

The description is front-loaded with purpose and usage, and most sentences carry useful information. It is somewhat verbose in explaining profile output fields even though an output schema exists, but it remains structured and readable.

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?

The definition covers purpose, usage context, workspace scope, output semantics, and cross-tool guidance. Given the simple one-parameter schema, annotations, and output schema, an agent has what it needs to select and call this tool correctly.

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 only parameter, limit, already has 100% schema coverage with minimum, maximum, and default. The description restates the same range and default but adds no additional meaning about the parameter's behavior.

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 states a specific verb and resource: list caller personas/profiles in the workspace, newest first. It also distinguishes the tool by explaining its role in mission-test configuration and naming a related sibling for a different query.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: when the user is setting up or drafting a mission test without naming a persona, or asks which personas exist. It also routes the agent to listMissionTestConfigs for checking which persona existing tests use.

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

All Nopaque TotalPath 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.