Skip to main content
Glama

Typebar (formerly SuperDocs)

request_limit_increase

Request a higher scale limit for your account in ONE call.

WHEN TO USE: after any 413 with error_code DOCUMENT_TOO_COMPLEX (a single document crossed the standard per-document page limit) or SESSION_TOO_FULL (the documents open in one chat crossed the standard per-chat limit). These are stability limits, not hard caps: the platform supports larger deployments, and limits are raised per account on request.

WHAT HAPPENS: the Typebar team is notified immediately with your account identity and the numbers you send; limits are typically expanded within a day and you are contacted at your account email. No email writing needed — though hello@superdocs.app also works if you prefer.

ALTERNATIVES while you wait: split the file into smaller documents, upload it as an attachment (reference/search, not editing), start another session for additional documents (init_session), or close documents you no longer need (close_session_document).

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": "request_limit_increase"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat you hit: 'document_scale' = a single document crossed the per-document page limit (413 DOCUMENT_TOO_COMPLEX); 'session_scale' = the documents open in one chat crossed the per-chat limit (413 SESSION_TOO_FULL); 'other' = anything else (explain in note).document_scale
noteNoAnything else that helps us size your limits (workload, cadence, deadline).
filenameNoThe file that hit the limit, if any.
attempted_pagesNoApproximate page count you were trying to work with (from the 413 message).
attempted_sectionsNoExact section count from the 413 detail (section_count / document_section_count), if you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so well: it discloses the side effect (Typebar team notified with account identity and the numbers sent), the SLA (typically within a day), and the response channel (account email). It does not say what the tool itself returns or whether a request can be duplicated/withdrawn, which is the only remaining gap for a submission-style tool.

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?

Front-loaded with the core action, then cleanly sectioned into WHEN TO USE, WHAT HAPPENS, and ALTERNATIVES — easy to scan and every block is actionable. Mildly long, and the 'hello@superdocs.app also works' aside could be dropped without loss.

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?

All five parameters are optional and fully schema-described, there is no output schema to explain, and the description covers trigger, side effects, latency, and fallbacks. Nothing an agent needs in order to call this correctly or explain the outcome to a user is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains kind, note, filename, and the attempted_pages/sections distinction. The description corroborates the error-code-to-kind mapping and hints that the numbers are used for sizing, but adds no syntax or constraint detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource ('request a higher scale limit for your account') with scope and effort ('in ONE call'), and explicitly ties it to error conditions that no sibling tool addresses. An agent can immediately distinguish it from close_session_document or init_session, which are named only as mitigations, not substitutes.

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?

A dedicated WHEN TO USE block names the precise trigger conditions (413 with DOCUMENT_TOO_COMPLEX or SESSION_TOO_FULL) rather than vague 'when you need more limits'. It also supplies four concrete workarounds with sibling tool names for the interim, so the agent knows both when to call this and what else it can do instead.

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.