Skip to main content
Glama
oetiker

MCPretentious

by oetiker

mcpretentious-resize

Resize a terminal to specific width and height in columns and rows. Specify terminal ID, columns, and rows to adjust the terminal dimensions.

Instructions

Resizes a terminal to the specified dimensions in columns × rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
terminalIdYesThe terminal ID to resize
columnsYesNumber of columns (width in characters)
rowsYesNumber of rows (height in lines)
Behavior2/5

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

No annotations are present, so the description must disclose all behavioral traits. However, it only says 'Resizes a terminal' without explaining side effects, instant effects, or what happens to existing content. No mention of required permissions or limitations.

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?

The description is a single sentence with no wasted words. It front-loads the action and resource, achieving maximum conciseness.

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 resize operation with clear parameters and no output schema, the description covers the basic action. However, it lacks usage context and behavioral details that would make it complete for an AI agent deciding when to invoke it.

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 coverage is 100%, so the schema already describes parameters. The description repeats 'columns × rows' but adds no new semantic meaning beyond formatting. Baseline 3 is appropriate as it does not contradict or subtract.

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 the tool's purpose: resizing a terminal to specified dimensions in columns × rows. The verb 'Resizes' and resource 'terminal' are specific, and the sibling tools indicate different actions (close, open, list), so this tool is well-distinguished.

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?

No guidance is provided on when to use this tool versus alternatives like mcpretentious-open or mcpretentious-list. The description does not mention prerequisites, scenarios, or exclusions.

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/oetiker/MCPretentious'

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