Autopo

Founder home

founder_home

Read-onlyIdempotent

What needs you, what improved and what is stuck in a company right now: the home screen's digest, the open decisions, running work, delivered work and your requests. Start here for 'what happened'.

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": "founder_home"
  }
}

Input Schema

Name	Required	Description	Default
`company`	No	the company id (list_companies); not needed when you have one company, asked for otherwise

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / company / description

Previous value: -"the company id (list_companies); optional when you have one"New value: +"the company id (list_companies); not needed when you have one company, asked for otherwise"

removedInput schema / required
```
Removed value: -[]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds that the result is a multi-section aggregate (digest + decisions + work + requests), which is useful beyond the annotations, but it says nothing about freshness, scoping, or volume of the aggregate. With annotations carrying the burden, a 3 fits.

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?

One dense sentence with the payoff phrase 'Start here for what happened' front-loaded at the end as a routing cue; nothing is wasted. The triple framing ('what needs you, what improved, what is stuck') is slightly more rhetorical than necessary but maps directly onto returned sections.

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?

An output schema exists, the tool is read-only and idempotent, and the only parameter is fully documented in schema — so the description needn't explain return values or pagination. It covers what an agent needs: what the digest contains and that it is the starting point. Only the relationship to sibling overview tools is left implicit.

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 a single optional `company` parameter and the schema already documents it at 100% coverage, including the list_companies pointer and the single-company default. The description adds nothing about the parameter, so baseline 3 applies — the schema does all the work here.

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 names the concrete content the call returns — the home-screen digest, open decisions, running work, delivered work and your requests — so an agent knows exactly what resource this is. What's missing is an explicit verb and an explicit differentiator from siblings like company_overview, activity and get_briefing, which also sound like 'what happened' summaries.

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?

'Start here for what happened' gives a clear entry-point condition and implies this precedes the more granular list_*/get_* tools. It stops short of explicitly naming alternatives or stating when not to use it, so an agent still has to infer that list_decisions or activity are the follow-ups.

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

All Autopo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?