Skip to main content
Glama

Finally Offline

by com.finallyoffline.www
OverviewDiscussionsAdmin

subscribe

Enable or disable digest access for your authenticated integration. Register first. Automatic webhook delivery is not enabled; omit webhook_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNofalse disables this subscription
agent_idNoOptional consistency check: must match your credential's server-generated ID
agent_nameNoOptional attribution label; does not change the registered profile
categoriesNoCategories to subscribe to: sports, music, fashion, culture, all
agent_tokenNoCredential from register_agent. Alternative to Authorization: Bearer. Never put it in URLs.
webhook_urlNoAutomatic webhook delivery is unavailable. Omit for digest access; null removes an existing webhook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your unique agent identifier"New value: +"Optional consistency check: must match your credential's server-generated ID"
    • changedInput schema / properties / agent_name / description
      Previous value: -"Human-readable name for your agent"New value: +"Optional attribution label; does not change the registered profile"
    • addedInput schema / properties / agent_token
      Added value: +{
+  "description": "Credential from register_agent. Alternative to Authorization: Bearer. Never put it in URLs.",
+  "type": "string"
+}
    • addedInput schema / properties / enabled
      Added value: +{
+  "default": true,
+  "description": "false disables this subscription",
+  "type": "boolean"
+}
    • changedInput schema / properties / webhook_url / description
      Previous value: -"URL where we'll POST new articles (must be HTTPS)"New value: +"Automatic webhook delivery is unavailable. Omit for digest access; null removes an existing webhook."
    • changedInput schema / properties / webhook_url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "agent_id",
-  "webhook_url"
-]New value: +[]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate the tool is not read-only and not destructive, so the description carries the burden of explaining what it actually does. It explains enabling/disabling a digest subscription, and it adds non-obvious operational constraints: registration must already exist and webhook delivery is unavailable.

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 short sentences deliver the action, the precondition, and the key caveat without filler. The structure is front-loaded with the purpose and then gives the most important usage warning.

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?

The schema fully documents each parameter Ia, and the description adds the registration prerequisite and webhook unavailability, which are essential and not inferable from the schema. A mention of the return value would be nice, but the tool is simple enough that this is not a blocking 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?

The schema already describes all six parameters, so the description does not need to add much parameter-level detail. The 'omit webhook_url' note is useful but largely duplicates the schema's own description of the webhook_url field.

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?

The description states a precise action and resource: enable or disable digest access for an authenticated integration. It also distinguishes itself from registration by saying 'Register first,' and it clarifies that this is not webhook delivery by instructing to omit webhook_url.

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?

'Register first' establishes an explicit precondition, and 'Automatic webhook delivery is not enabled; omit webhook_url' gives a clear when-not instruction. It does not name sibling alternatives like generate_digest, but the registration prerequisite and webhook caveat are enough to guide appropriate use.

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

All Finally Offline 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