Skip to main content
Glama

review_routes

Review multiple routes of an application to measure motion—durations, easing curves, stagger intervals, exit timing, reduced-motion support—scored against animation standards.

Instructions

Review multiple routes of an application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNo
formatNo
routesYes
base_urlYes
new_onlyNoReport only findings not seen in prior runs of each route.
providerNo
viewportsNo
max_findingsNoKeep only the top N findings per route, severity-ordered.
max_pr_annotationsNoSARIF only: emit at most N results per route report, severity-ordered.
Behavior1/5

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

No annotations are provided, so description must fully disclose behavioral traits. It only says 'review', giving no indication of read/write nature, side effects, or output characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single sentence, but it is under-specified rather than concise. Key information is missing; it cannot be considered efficiently structured.

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

Completeness1/5

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

With 9 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to cover return values, behavior, or how results are presented.

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

Parameters1/5

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

Schema description coverage is only 33% (3 of 9 params documented). The description adds no parameter meaning beyond the schema; it does not explain the undocumented params like model, format, provider, viewports.

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

Purpose4/5

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

Description states 'Review multiple routes of an application' which is a clear verb-resource combination. However, it does not differentiate from sibling tools like review_url (single URL) or review_flow (likely a sequence), missing an opportunity to clarify scope.

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 on when to use this tool versus alternatives. No prerequisites, limitations, or context for usage provided.

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/bobaba99/motionlint'

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