Skip to main content
Glama

taskwall_view

Retrieve tasks sorted by score across short, mid, and long term horizons. Enables leaders to quickly prioritize and identify next actions.

Instructions

Get the task wall view — categorized by short/mid/long term with intelligent sorting.

Returns a task list sorted by score, helping Leader quickly understand what to do next.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
horizonNoFilter by time horizon, one of "short" / "mid" / "long" (empty = all)
team_idYesTeam ID or name
priorityNoFilter by priority, one of "critical" / "high" / "medium" / "low", comma-separated for multiple (empty = all)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. Description mentions 'intelligent sorting' and 'sorted by score' but doesn't explain what 'intelligent' means, auth needs, or side effects. Falls short of full behavioral disclosure.

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?

Two sentences, front-loaded with key info. Could be slightly more concise but overall efficient.

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?

Output schema exists, so return values are covered. Parameters fully described. Missing usage guidelines and behavioral details for a complete picture.

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 parameters are already well-documented. Description adds minimal value beyond schema, only reinforcing the horizon categorization.

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?

Clearly states 'Get the task wall view' with specific resource and categorization by time horizon. Differentiates from sibling tools like task_list_project which list tasks differently.

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 vs alternatives like task_list_project or task_compare. No mention of prerequisites or context.

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/CronusL-1141/AI-company'

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