Skip to main content
Glama

Get upload limits

get_limits
Read-only

Current limits per type: sizes in bytes, counts, TTLs in days.

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

Input Schema

NameRequiredDescriptionDefault
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  2. Changed1 schema field changed
    • addedInput schema / properties / ownerToken
      Added value: +{
      +  "description": "Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint=true annotation already declares this is a safe read, so the description only needs to add context such as whether limits vary by owner, whether values are cached, or whether an unauthenticated call returns defaults. It adds none of that. The one behavioral detail it does supply — that values are expressed in bytes and days — is genuinely useful to avoid unit errors.

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?

A single compact sentence that front-loads the substantive content with no filler, and the unit clarifications (bytes, days) are exactly the kind of detail worth spending words on. The terseness tips into under-specification, but nothing is redundant.

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

Completeness2/5

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

With no output schema and no schema descriptions, the description must carry nearly everything, and it does not explain what a "type" is, what the response object looks like, or how ownerToken affects the result. For a limits-lookup tool these omissions leave the agent guessing at the key semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single optional parameter ownerToken is not mentioned in the description at all, so the agent cannot tell whether omitting it returns global defaults or an error, or whose limits are returned when it is supplied. The description's unit notes apply to outputs, not to this input parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the content returned ("limits per type: sizes in bytes, counts, TTLs in days") but never says plainly that it retrieves upload limits, and "per type" is left undefined — types of what (file, page, KV?). The title supplies "upload limits" while the description supplies the return shape, so together they are workable but neither is decisive on its own.

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

Usage Guidelines2/5

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

There is no statement of when an agent should call this rather than another tool, no prerequisite or auth context, and no mention of the ownerToken parameter's effect on results. The agent must infer that this is a pre-flight lookup before a publish/upload call from the sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.