Skip to main content
Glama
chrischall

onehome-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List my OneHome agent groups

onehome_get_groups
Read-onlyIdempotent

List the OneHome groups your agent has shared with you. Set include_contacts to true to also retrieve member emails and agent contact details.

Instructions

List the OneHome groups your agent has shared with you. Share member e-mails and the agent's e-mail/phones are omitted unless include_contacts: true. For full agent / registered users, returns the GraphQL user.groups list. For magic-link consumer-share sessions (a single shared group), synthesizes a one-entry list from the checkToken session context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_contactsNoInclude contact details: the share's member e-mail addresses and the agent's e-mail, phone and office phone. Default false — the agent's name, office and team are always returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • addedInput schema / properties / include_contacts
      Added value: +{
+  "description": "Include contact details: the share's member e-mail addresses and the agent's e-mail, phone and office phone. Default false — the agent's name, office and team are always returned.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.13.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, so the safety profile is covered. The description adds real behavioral context: contacts are withheld by default, and the return shape differs by session type (GraphQL user.groups vs a synthesized one-entry list from checkToken). This is useful disclosure beyond the annotations.

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?

Three tight sentences, front-loaded with the core purpose before the contact-omission rule and the two return modes. No filler, though the density of GraphQL/checkToken terms slightly burdens the opening read.

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?

There is no output schema, so the description carries the return-value burden and does reasonably well by naming the two return shapes (user.groups vs one-entry synthesized list). It stops short of describing field-level contents or ordering, but for a single-optional-param read tool it is largely complete.

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 description coverage is 100%, so the schema already documents include_contacts fully, including the always-returned fields. The description restates the same omission behavior ('omitted unless include_contacts: true') without adding format or default nuance, so 3 is the correct baseline.

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?

Specific verb+resource ('List the OneHome groups your agent has shared with you'), stating both the operation and its scope. It doesn't need to differentiate from siblings since none of the other tools list groups, but it also makes no attempt to position itself against them.

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

Usage Guidelines3/5

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

The description explains the two session contexts (full agent vs magic-link consumer-share) in which the tool behaves differently, which implicitly tells the agent when it applies. However, there is no explicit 'use this when / use X instead' guidance, nor any prerequisite or exclusions.

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

Deploy Server

Other Tools