Skip to main content
Glama
Sign In
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Retrieves the workspace limits.

get_limits
Read-onlyIdempotent

Retrieves the current limits for a specified workspace, using -1 to target the default workspace.

Instructions

This method returns the current limits for the specified workspace.

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
workspaceIdNoWorkspace identifier. -1 means the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing beyond that: it does not say what the limits represent, whether they change over time, or what happens when workspaceId is omitted (the schema default -1 handles that instead).

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, front-loaded sentence with no filler or repetition. It is economical, though its brevity contributes to the under-specification noted in other dimensions.

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

Completeness3/5

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

For a simple read-only, single-optional-parameter tool with full annotation coverage and no output schema, little is strictly required. However, the central ambiguity — what 'current limits' actually contains — is left unresolved, which is the one thing the description should have clarified.

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% and the single parameter is fully documented in the schema, including the -1 default meaning. The description only echoes 'specified workspace', adding no syntax or semantic detail beyond the schema, so the baseline 3 applies.

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 gives a clear verb and resource ('returns the current limits'), but 'limits' is undefined — it could mean plan/tariff quotas, proxy limits, or profile limits, especially with get_tariff in the sibling set. There is no differentiation from siblings that might also surface quota-like data.

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 when-to-use guidance, no mention of prerequisites, and no alternatives (e.g., get_tariff for plan-level information). The agent must infer the use case entirely.

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

Deploy Server

Other Tools