Samuelz® Policy

Get connected operator profile

get_profile

Read-onlyIdempotent

Read the current authenticated profile for this workspace. Use get_context for workspace/scopes and initial tool discovery.

Each call reads the stored opaque id and available name/email/nickname, without a tool-level cache. The id binds workspace and user: profile edits keep it stable; another workspace changes it. It is not a native user ID.

Invalid authentication fails. This tool has no account selector and cannot sign in, switch accounts or grant access.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	No
`email`	No
`nickname`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond annotations: no tool-level cache, the opaque id binds workspace and user, profile edits keep it stable, another workspace changes it, and invalid authentication fails. It also clarifies what the tool cannot do.

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 the core purpose and alternative tool, then adds behavioral details. It is generally efficient, though it spans three paragraphs and includes a few details such as 'Invalid authentication fails' that are useful but slightly verbose for a zero-parameter read tool.

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?

Given the tool has no parameters, rich annotations, and an output schema, the description provides all the context an agent needs: return fields, id stability semantics, authentication failure behavior, and explicit limitations. Nothing critical is missing.

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?

The tool has zero parameters, so parameter semantics are not the main concern. The description mentions return fields such as opaque id, name, email, and nickname, but no parameter-level semantics are needed. Baseline for zero parameters is appropriate.

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: 'Read the current authenticated profile for this workspace.' It also explicitly distinguishes itself from get_context, which is for workspace/scopes and initial tool discovery. An agent can identify what this tool does without opening the schema.

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?

The description names the alternative tool and its purpose ('Use get_context for workspace/scopes and initial tool discovery') and states clear exclusions: no account selector, cannot sign in, switch accounts, or grant access. This gives explicit when-to-use and when-not-to-use guidance.

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

All Samuelz® Policy 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.

Resources

Need Help?