Skip to main content
Glama
Sign In

FamilyLore

by ai.familylore
OverviewDiscussionsAdmin

Send a photo

upload_slot

A one-time link where the person sends FamilyLore the photo of a page, for FamilyLore's card.

Input Schema

NameRequiredDescriptionDefault
yearNoThe year it was written, if known
languageNoThe letter's language, if known
target_languageNoThe language to translate it into: en (English), de (German), ru (Russian), pl (Polish), it (Italian), fr (French), uk (Ukrainian). English if left out.

Output Schema

NameRequiredDescriptionDefault
linkYesWhere the person sends the photo: once, before expires_at
page_idYesThe page the photo becomes; get_reading shows its reading
expires_atYesWhen the link stops working (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / target_language / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "en",
-      "de",
-      "ru"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "en",
+      "de",
+      "ru",
+      "pl",
+      "it",
+      "fr",
+      "uk"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / target_language / description
      Previous value: -"The language to translate it into: en (English), de (German), ru (Russian). English if left out."New value: +"The language to translate it into: en (English), de (German), ru (Russian), pl (Polish), it (Italian), fr (French), uk (Ukrainian). English if left out."
  2. Changed1 schema field changed
    • changedInput schema / properties / language / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "ru_uk",
-      "de_kurrent",
-      "yi"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "ru_uk",
+      "de_kurrent",
+      "yi",
+      "en"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  3. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already state readOnly=false, idempotent=false, destructive=false, and openWorld=false. The description adds a useful behavioral detail by calling it a 'one-time link,' which reinforces single-use behavior, but it does not clarify creation vs. upload, permissions, or lifecycle.

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?

The description is a single focused sentence with no wasted wording. Its structure is a fragment rather than an action statement, but it is appropriately sized and front-loads the one-time-link concept.

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

Completeness2/5

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

Although an output schema and annotations exist, the description does not make the tool's core action explicit. For an agent deciding whether to call upload_slot versus other tools, the missing purpose/usage detail leaves a significant gap.

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%, and all three optional parameters have clear descriptions in the schema. The description adds no parameter-level meaning, so the schema carries the burden and baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the domain: a one-time link for sending FamilyLore a photo of a page. However, it is a noun phrase rather than a clear action verb, so an agent cannot tell whether the tool creates the link, returns the link, or performs the upload. It is not mere tautology, but the purpose remains vague.

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 explicit when-to-use guidance, no exclusions, and no comparison to sibling tools. The phrase 'for FamilyLore's card' hints at a use case, but the agent is left to infer the triggering conditions.

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

All FamilyLore toolsInspect
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