ai-content-drop

Get account

get_account

Read-onlyIdempotent

Check the signed-in account's remaining credits and current plan name before generating, and get the informational page about plans and entitlement. SIGN-IN REQUIRED: connect this server with OAuth (the host prompts for it), or add an API key header "Authorization: Bearer acd_live_…" created at https://aicontentdrop.com/settings/integrations.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	No
`plan`	Yes	free \| starter \| professional \| ultra \| enterprise_max
`info_url`	Yes	Informational page describing plans and entitlement options.
`username`	No
`can_generate`	Yes
`credits_remaining`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 9, 2026

addedOutput schema / properties / can_generate
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / info_url

Added value: +{
+  "description": "Informational page describing plans and entitlement options.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "plan",
-  "credits_remaining"
-]New value: +[
+  "plan",
+  "credits_remaining",
+  "can_generate",
+  "info_url"
+]

Changed1 schema field changedSep 1, 2026
- addedInput schema / required
```
Added value: +[]
```
First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds valuable behavioral context beyond those annotations, especially the OAuth or API-key authentication requirement, though it does not discuss rate limits or failure behavior.

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 front-loaded with the core purpose and usage context, followed by the authentication requirement. Both sentences earn their place, and the auth details are necessary for successful invocation.

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 timing, and authentication prerequisites. Because there are no parameters and an output schema exists, return-value details and parameter documentation are not needed in the description.

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 no parameters, so there are no parameter semantics to explain beyond the schema. With zero parameters and full schema coverage, the baseline of 4 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 uses a specific verb, 'Check,' and names the exact resources: signed-in account remaining credits and current plan name, plus plan/entitlement information. It is clearly distinct from sibling generation and canvas tools because it is account-status retrieval, not content generation or editing.

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 usage context by saying to use it 'before generating,' and it states the sign-in prerequisite explicitly. It does not name alternatives or when not to use it, which keeps it below a 5.

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

All ai-content-drop 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.