Skip to main content
Glama
remoet-labs

remoet

Official
by remoet-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

View Usage

get_usage
Read-only

Get your current usage against all enforced budgets: star count, monthly unstar budget, and daily MCP and REST API requests, each with a reset timestamp.

Instructions

Get the user's current usage against every budget the platform enforces: active star count vs star cap, unstars used this month vs monthly unstar budget, MCP requests made today vs daily MCP cap, REST API requests made today vs daily REST cap. Each budget includes a "resetsAt" ISO timestamp so you can tell the user exactly when the counter clears.

Calling this tool is free: it does not count against the daily MCP cap or the API key's request count, so check eagerly. Call it when the user asks "how close am I to my limit?" or "when does X reset?", or before firing 3+ write tools in a row (star_listing, update_profile, apply_to_job, etc.) so you can pace yourself. A limit value of "unlimited" means no cap for that budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already mark readOnlyHint: true. Description reinforces safety by stating it doesn't count against daily MCP cap or API request count, adding value beyond annotations. No contradiction.

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?

Well-structured, front-loads purpose, then details each budget and resetsAt. Every sentence adds value, with no redundancy.

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 no parameters and no output schema, the description fully covers the tool's behavior, return format, and use cases. Complete for a simple read-only tool.

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?

No parameters exist (0 params), so baseline is 4. No additional parameter info needed.

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 clearly states it gets current usage against enforced budgets, listing specific metrics (star count, unstars, MCP requests, REST requests). It distinguishes itself from sibling tools as the only one reporting usage caps and resets.

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?

Explicitly describes when to call: when user asks about limits/resets, or before performing multiple write operations. Also notes it's free and doesn't count against caps, guiding eager use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/remoet-labs/remoet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server