Familia

Search family board items

familia_search_items

Read-only

Use this when the user asks to find Familia tasks, plans, or connected calendar events by title, notes, description, or location. Do not use for public web search or unrelated document search.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of matches to return. Defaults to 12.
`query`	Yes	Search text, e.g. "dentist", "school trip", or "groceries".
`offset`	No	Pagination offset, defaults to 0.
`timezone`	No	IANA timezone used when formatting matched timeline items.
`householdId`	No	Optional Familia household id. Omit to search all accessible households.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`hasMore`	Yes
`matches`	Yes
`totalCount`	Yes
`securityNotice`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedSep 7, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Pagination offset, defaults to 0.",
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / totalCount
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / required

Previous value: -[
-  "query",
-  "securityNotice",
-  "count",
-  "matches"
-]New value: +[
+  "totalCount",
+  "hasMore",
+  "query",
+  "securityNotice",
+  "count",
+  "matches"
+]

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so no safety contradiction exists. The description adds little behavioral detail beyond searching, but nothing contradicts annotations; baseline is appropriate.

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 concise sentences with no redundant wording. Key purpose and exclusion are front-loaded, making it easy for an agent to parse quickly.

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?

Given the simple read-only search nature, the description is complete. Output schema is present, so return values do not need to be described. No critical operational context 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 covers all parameters at 100%, and the description adds meaningful semantic context by specifying the searchable fields (title, notes, description, location). This goes slightly beyond the raw schema.

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 clearly states the action ('find') and the specific resource ('Familia tasks, plans, or connected calendar events'), along with the searchable fields. This makes its purpose distinct and immediately recognizable.

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?

Provides explicit when-to-use guidance ('Use this when the user asks to find...') and a clear negative directive ('Do not use for public web search or unrelated document search'). However, it does not name alternative sibling tools to prefer in those negative cases.

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

All Familia tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?