Skip to main content
Glama

Coline

Show Home

show_home
Read-onlyIdempotent

Shows the person's Coline Home inside the chat: what waits on them, today's meetings and tasks, overdue work, and what they were working on. Use it when they ask what's on today, what needs them, or where they left off.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "show_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
todayYes
recentYes
overdueYes
dueTodayYes
needsYouYes
timeZoneYes
waitingOnYouYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile needs no restating. The description adds value by revealing that this is a composed, cross-domain snapshot (meetings + tasks + overdue + recents) rather than raw records. It says nothing about scope limits, whether results are per-user or per-workspace, or freshness of the data.

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?

Two sentences: the first defines what is shown and its components, the second defines when to use it. Front-loaded, no filler, no restatement of the title.

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

Completeness4/5

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

With an output schema present, return values need not be described, and the single required parameter is fully covered by the schema. The description's content enumeration plus usage triggers are enough to call it correctly. A note on workspace scoping or data freshness would close the remaining gap.

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?

There is one parameter at 100% schema description coverage, and the schema already documents the workspace slug with a format example ("acme") and a pointer to workspaces.list. The description adds no further meaning about that parameter, which is the expected baseline when the schema does the work.

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?

The description gives a specific verb and resource ("Shows the person's Coline Home inside the chat") and enumerates its contents — pending items, today's meetings and tasks, overdue work, recent activity. That makes the aggregate/dashboard nature clear versus single-domain siblings like show_calendar or show_board, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies concrete trigger phrases: "what's on today, what needs them, or where they left off." That tells the agent when to reach for this aggregate view rather than a domain-specific show_* tool. It stops short of explicit exclusions (e.g., use show_calendar for a full calendar) or prerequisites such as resolving the workspace first.

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.

Resources