Marcora

get_current_user_info

Read-onlyIdempotent

Returns profile and subscription information for the currently authenticated user. Use this to personalize responses, check the user's active team, or confirm subscription limits before creating content.

Key fields:
- active_team_name / active_team_role: current working team context
- subscription_status + plan_name: confirms what features are available
- ai_credits_available / ai_credits_max: Studio Credits remaining and the plan's limit for the current billing period

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_current_user_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`name`	Yes	User's full name.
`email`	Yes	User's email address.
`plan_name`	No	Subscription plan name (e.g. Marcora Business).
`plan_slug`	No	Plan identifier slug (e.g. business, starter).
`ai_credits_max`	No	Studio Credit limit for this billing period.
`active_team_name`	Yes	Name of the user's currently active team.
`active_team_role`	Yes	User's role in the active team (e.g. admin, member).
`subscription_status`	No	Team subscription status (e.g. active, trialing, canceled).
`ai_credits_available`	No	Studio Credits remaining this billing period (max minus used).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds value by enumerating which fields come back (team context, subscription status/plan, AI credits), but says nothing about authentication requirements, failure behavior when no session exists, or freshness of the credit figures.

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 purpose sentence is front-loaded and the bulleted key-fields block is scannable, with every listed field tied to a concrete use case. It is slightly longer than necessary given that an output schema already exists and could carry the field inventory on its own.

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 zero parameters, an existing output schema, and annotations that fully cover the safety profile, the description covers everything an agent needs to select and invoke this tool correctly. The added field summary helps the agent decide whether the call answers its question.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema is an empty object, which the description correctly leaves alone rather than padding with irrelevant detail.

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?

The description gives a specific verb and resource: 'Returns profile and subscription information for the currently authenticated user.' The phrase 'currently authenticated user' naturally scopes it apart from team-scoped siblings like get_team_info, but no sibling is named explicitly, so the differentiation is only implied.

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 supplies concrete when-to-use triggers: personalize responses, check the user's active team, and confirm subscription limits before creating content. That last clause is a useful just-in-time routing cue. It stops short of stating when not to use it or naming the alternative tool for team-level data.

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

All Marcora 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?