Skip to main content
Glama

rocketsloth

by ai.rocketsloth

Check Application Status

application_status

Check an application's status using its application token (at_...). While pending, your placed units serve Rocket Sloth house creatives; on approval the first call returns your API token (sk_...) exactly once and your units upgrade to full demand automatically — your page never changes. A Bearer web session (the in-page agent on rocketsloth.ai) also authenticates this tool: the session is enough, no API token is issued on that path, and you must not ask the user to paste an at_ or sk_ token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNoYour application token (at_...). May instead be sent as an Authorization: Bearer header.

TDQS

A4/5.0
Behavior4/5

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

Discloses that the first call after approval returns the API token only once, and that units upgrade to full demand automatically, indicating side effects beyond a simple read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose, repeating authentication details, but remains focused.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides necessary context about authentication methods and behavioral changes, covering the tool's purpose effectively.

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 schema describes the token parameter, and the description reiterates it, clarifying it can be sent via header.

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?

Clearly states the tool checks application status using a token. Distinct from siblings like 'apply' or 'reporting'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this over other tools, but the description provides context on behavior during pending/approved states, implying when to check.

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

All rocketsloth toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a distinct purpose and clear descriptions. Names like 'reclaim' and 'recover' refer to different operations, and 'ad_settings' vs 'reporting' are easily separable. No overlapping functions are apparent.

Naming Consistency3/5

Tool names mix nouns (account, payments, video) and verbs (apply, ask, reclaim) and use inconsistent naming conventions (snake_case for compound names like ad_settings, but single words elsewhere). There is no uniform verb-noun pattern or prefix.

Tool Count5/5

14 tools is a reasonable and comprehensive set for a publisher/ad platform covering onboarding, account management, ads, reporting, payments, subscriptions, video, and recovery. It is neither sparse nor bloated.

Completeness5/5

The tool set covers the full lifecycle from application (apply, application_status) through integration (integration, checklist), account management (account, ad_settings), monetization (reporting, subscriptions, video), and recovery (reclaim, recover). No obvious gaps for the stated domain.

Resources