Skip to main content
Glama

SesApp Access Sheets

by fr.sesapp
OverviewDiscussionsAdmin

update_fiche

Update an owned access sheet. Same fields as create_fiche. Typical: update instructions with photos/links. Requires Bearer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
latNoCover map + WiFi geofence (150 m).
lonNoCover map + WiFi geofence (150 m).
nameNo
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.
formattedAddressNo

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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Requires Bearer' is a useful auth disclosure, but the description says nothing about what happens to omitted fields (overwrite vs merge), whether the update is destructive, error behavior, rate limits, or the 150 m geofence implications that are buried in the schema. For a mutation tool with zero annotation coverage, this is a significant 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?

Three short clauses, front-loaded with the action and resource, no wasted words. However, the telegraphic style ('Same fields as create_fiche') leaves the reader to infer details rather than stating them, which trades clarity for brevity.

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?

Given 11 parameters, no output schema, and no annotations, the description is thinner than ideal. It does hint at the sibling schema and the auth requirement, but omits mutation semantics, field-omission behavior, and any return information. Adequate as a minimum viable pointer, not complete for a mutation tool of this complexity.

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 coverage is 73%, so most parameters have descriptions already. 'Same fields as create_fiche' adds a small pointer to the sibling's schema but no new parameter meaning. The 'typical: ... photos/links' note maps loosely to instructions, but the description adds little beyond the schema's already-rich instructions documentation.

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 specific verb and resource ('Update an owned access sheet') and distinguishes itself from create_fiche by referencing 'Same fields as create_fiche.' The ownership qualifier ('owned') also implicitly contrasts with share_fiche and get_fiche, though it doesn't explicitly route to alternatives.

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?

Provides a narrow 'typical' use case (update instructions with photos/links) which hints at usage, but offers no explicit when-to-use/when-not guidance, no indication of when to prefer create_fiche vs update_fiche, and no prerequisites beyond a terse 'Requires Bearer' note.

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