Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_notifications

Retrieve recent Foto account notifications—likes, comments, mentions, and follows—to monitor community interactions and stay updated.

Instructions

Retrieve recent notifications and community interactions on your Foto account (likes, comments, mentions, follows).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum notifications to retrieve (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does little beyond 'Retrieve'. It does not say whether authentication/authorization is required, whether results are ordered newest-first, whether reading marks notifications as read, or whether pagination exists beyond the single limit cap.

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?

A single front-loaded sentence with the resource scope first and the parenthetical type list last; nothing is redundant. It is efficient, though the parenthetical enumeration slightly stretches the sentence.

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

Completeness3/5

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

For a simple read tool with one optional parameter, the description covers what is fetched and which notification categories appear, partially compensating for the absent output schema. It still leaves auth requirements, ordering, and read-state side effects unaddressed, which an agent would need to call it confidently.

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?

The only parameter (limit) is fully documented in the schema, including the default of 20 and the maximum of 50. The description adds no meaning about how the limit interacts with recency or ordering, so the baseline of 3 for complete schema coverage applies.

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 states a specific verb ('Retrieve') and resource ('recent notifications and community interactions') and enumerates the event types returned (likes, comments, mentions, follows). That enumeration separates it from narrow siblings such as foto_get_post_likes or foto_get_comments, though it never names an alternative outright.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no routing to relevant siblings such as foto_dismiss_notification (for clearing items) or the feed tools. The agent must infer that this is the aggregate notification inbox from the word 'notifications' alone.

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