Skip to main content
Glama
IsidoreSoftware

Ogarni.AI MCP Server

by IsidoreSoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Groups

ogarniai_list_groups
Read-onlyIdempotent

List finance groups you belong to for shared expenses with partners or family. Optionally show archived groups to keep a complete record.

Instructions

List finance groups the user belongs to.

Groups allow sharing expenses with a partner or family members.

Args:

  • showArchived (boolean, optional): Include archived groups (default: false)

Returns: JSON array of groups with id, name, description, ownerId, isActive, isArchived, memberCount, createdAt

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showArchivedNoInclude archived groups

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds the default behavior for showArchived (false) and enumerates the returned fields, which is meaningful beyond the schema.

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?

The description is compact and front-loaded: one purpose sentence, one args line, one returns line. No boilerplate or redundant content.

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

Completeness5/5

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

For a simple, read-only list operation with one optional parameter and no output schema, the description covers scope, defaults, and return fields. Nothing needed for correct invocation is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds the default value of showArchived and clarifies the result is scoped to the user, moving it above baseline.

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?

Description states a specific verb ('List'), resource ('finance groups'), and scope ('the user belongs to'). This is clearly distinguishable from sibling list tools like list_documents or list_notifications.

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?

The intended use is clear: list groups tied to the current user, with an optional flag for archived groups. It doesn't explicitly compare with alternatives like get_group, so it isn't a 5, but no guidance is missing for typical selection.

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