Skip to main content
Glama
Sign In

Recipe Reels

by com.recipe-reels
OverviewDiscussionsAdmin

whoami

Read-only
The connected account's own profile: its tier (user, subscriber or
admin), username (`display_name`), email, and the agents connected to it. Call this
right after connecting: the tools marked "requires Subscriber" fail
with an explanation for a user-tier account, so knowing the tier up
front saves a wasted call.

Input Schema

NameRequiredDescriptionDefault
session_tokenNoThe session token check_agent_connection returned for the connected account. Required, unless it's sent as an Authorization: Bearer header on the MCP request instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description goes beyond the structural annotations by explaining the real-world implication of the tool's output: knowing the user's tier dictates which subsequent calls will succeed or fail. This operational context provides significant behavioral value to the agent.

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?

The description is highly efficient, dedicating the first part to 'what it is' and the second part to 'why and when to use it.' The critical workflow guidance is front-loaded, making the text very scannable and impactful.

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 annotations cover safety (read-only), the description is complete. It defines the input context (post-connection) and the expected structure of the output (user profile details). No crucial information needed for correct invocation is omitted.

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?

Since the schema provides 100% coverage, the description primarily serves as high-level documentation. It does not add unique semantic meaning (e.g., data types, specific formatting) beyond what the input schema already provides. This meets the baseline for a 100% coverage tool.

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 explicitly states that the tool returns the connected account's complete profile, including specific fields like tier, username, and email. It clearly defines the resource being retrieved (the connected account's data), making its purpose unambiguous.

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 provides explicit workflow guidance, instructing the user to call this tool immediately after connection. Furthermore, it explains the strategic benefit of this call—determining the user tier to preemptively avoid errors in other subscriber-restricted tools.

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

All Recipe Reels toolsInspect
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