Skip to main content
Glama

SesApp Access Sheets

by fr.sesapp
OverviewDiscussionsAdmin

create_fiche

Create an access sheet. Write the guest flip-book in instructions (Markdown; guest language, usually French). Cover (map/name/address/accessCode) is auto. Pages: --- . Photos: alt. Intents: Add WiFi or Ajouter le WiFi + wifiName/wifiPassword; Add contact or Ajouter le contact + phoneNumber. Never put wifiPassword in Markdown (150 m GPS). Optional locale fr|en for guest chrome. Playbook: GET /llms.txt. Requires Bearer. Beyond quota, retry with PAYMENT-SIGNATURE (0.50 USDC on Agent, 0.25 on Fleet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoCover map + WiFi geofence (150 m).
lonNoCover map + WiFi geofence (150 m).
nameYes
localeNoGuest chrome language. Markdown stays as written. Omit to follow Accept-Language / ?lang=.
wifiNameNoSSID for sesapp:wifi. Hidden until 150 m if wifiPassword is set.
accessCodeNoShown on the generated cover.
phoneNumberNoRequired for sesapp:contact. E.164 preferred.
instructionsNoMarkdown flip-book shown to the guest (this field). Cover (map, name, formattedAddress, accessCode) is generated — do not repeat it here. Split pages with a line containing only --- . Supported: # ## ### headings, paragraphs, **bold**, *italic*, - / 1. lists, [label](https://...), ![alt](https://...). Photos: https URLs (GCS via the host app, or your own CDN). Agents send URLs, no file upload. Never put wifiPassword in Markdown; it is unlocked only within 150 m via GPS. Intent hrefs: sesapp:wifi (needs wifiName + wifiPassword) and sesapp:contact (needs phoneNumber). Guest-facing labels: [Ajouter le WiFi] / [Ajouter le contact]. If you omit those links but set the fields, SesApp appends WiFi/contact pages. Example: # Bienvenue Parking au fond à gauche. ![Façade](https://example.com/facade.jpg) --- ## Arrivée Sonnette à gauche. [Itinéraire](https://maps.google.com/?q=48.8566,2.3522) --- [Ajouter le WiFi](sesapp:wifi) --- [Ajouter le contact](sesapp:contact)
wifiPasswordNoDo not put in instructions. Unlocked within 150 m.
formattedAddressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / instructions / description
      Previous value: -"Markdown flip-book shown to the guest (this field).\nCover (map, name, formattedAddress, accessCode) is generated — do not repeat it here.\nSplit pages with a line containing only --- .\nSupported: # ## ### headings, paragraphs, **bold**, *italic*, - / 1. lists, [label](https://...), ![alt](https://...).\nPhotos: https URLs only. No file upload — host images yourself.\nNever put wifiPassword in Markdown; it is unlocked only within 150 m via GPS.\nIntent hrefs: sesapp:wifi (needs wifiName + wifiPassword) and sesapp:contact (needs phoneNumber). Guest-facing labels: [Ajouter le WiFi] / [Ajouter le contact].\nIf you omit those links but set the fields, SesApp appends WiFi/contact pages.\nExample:\n# Bienvenue\nParking au fond à gauche.\n\n![Façade](https://example.com/facade.jpg)\n\n---\n\n## Arrivée\nSonnette à gauche.\n\n[Itinéraire](https://maps.google.com/?q=48.8566,2.3522)\n\n---\n\n[Ajouter le WiFi](sesapp:wifi)\n\n---\n\n[Ajouter le contact](sesapp:contact)"New value: +"Markdown flip-book shown to the guest (this field).\nCover (map, name, formattedAddress, accessCode) is generated — do not repeat it here.\nSplit pages with a line containing only --- .\nSupported: # ## ### headings, paragraphs, **bold**, *italic*, - / 1. lists, [label](https://...), ![alt](https://...).\nPhotos: https URLs (GCS via the host app, or your own CDN). Agents send URLs, no file upload.\nNever put wifiPassword in Markdown; it is unlocked only within 150 m via GPS.\nIntent hrefs: sesapp:wifi (needs wifiName + wifiPassword) and sesapp:contact (needs phoneNumber). Guest-facing labels: [Ajouter le WiFi] / [Ajouter le contact].\nIf you omit those links but set the fields, SesApp appends WiFi/contact pages.\nExample:\n# Bienvenue\nParking au fond à gauche.\n\n![Façade](https://example.com/facade.jpg)\n\n---\n\n## Arrivée\nSonnette à gauche.\n\n[Itinéraire](https://maps.google.com/?q=48.8566,2.3522)\n\n---\n\n[Ajouter le WiFi](sesapp:wifi)\n\n---\n\n[Ajouter le contact](sesapp:contact)"
  2. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Guest chrome language. Markdown stays as written. Omit to follow Accept-Language / ?lang=.",
+  "enum": [
+    "fr",
+    "en"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses Bearer auth requirement, a quota-exceeded path with PAYMENT-SIGNATURE and per-tier pricing (0.50/0.25 USDC), and a real security constraint (wifiPassword must never appear in Markdown and is only unlocked within a 150 m GPS geofence). It does not state what the call returns (no output schema), which is the remaining gap.

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?

Front-loaded with the core action and the authoring format, then security, then payment/auth. The telegraphic style is dense but nearly every clause carries load. Minor redundancy where the wifiPassword warning is repeated in both the top-level description and the instructions parameter.

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?

For a 10-parameter mutation tool with no annotations and no output schema, the description covers the essentials an agent needs: payload format, required fields, security rules, auth, and the paid-retry path. It is only short of describing the created resource or its identifier, which an agent might reasonably expect.

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 coverage is 80% so the baseline is 3, but the description adds genuine semantics the schema lacks: how wifiName/wifiPassword bind to the sesapp:wifi intent, how phoneNumber binds to sesapp:contact, the bilingual intent-label forms, and the fact that omitting the links while setting fields still appends WiFi/contact pages. That interaction logic is not recoverable from the schema alone.

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?

States a concrete verb+resource ('Create an access sheet') and immediately defines what the primary payload is. It is distinguishable from get_fiche/update_fiche/delete_fiche by the 'create' verb, though it never names those siblings explicitly to draw the boundary.

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?

Usage is implied through the heavy formatting/authoring instructions, but there is no explicit when-to-use versus update_fiche, and no statement of when not to call it (e.g. reuse of an existing fiche). The agent must infer the create-vs-modify split from the name.

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

All SesApp Access Sheets 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