Skip to main content
Glama
Sign In

Datailo: one MCP connection to tenders, EU regulation and law

by com.datailo
OverviewDiscussionsAdmin

Enable a service

datailo_enable
Idempotent

Sign-in required: call datailo_connect(email) and datailo_connect_verify first (free, one email) unless this connection is already signed in. Enable a federated service on your Datailo account. For services with an account model the hub links (or creates) your account there by your email and keeps an encrypted key; keyless services are enabled as a trial. Then datailo_tools and datailo_invoke reach it through this one connection.

Input Schema

NameRequiredDescriptionDefault
planNo
serviceYes
sessionNoThe `session` value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / session / description
      Previous value: -"The `session` value datailo_connect_verify returned, when this client keeps no connection session. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."New value: +"The `session` value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."
  2. Changed1 schema field changed
    • addedInput schema / properties / session
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The `session` value datailo_connect_verify returned, when this client keeps no connection session. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.",
+  "title": "Session"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only declare the general safety profile (non-readOnly, openWorld, idempotent, non-destructive). The description adds substantive side-effect detail the annotations cannot: sign-in is required, the hub links or creates an account on the target service using your email, it stores an encrypted key, and keyless services are enabled as a trial (a billing implication). This is exactly the kind of behavioral context annotations don't carry.

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-loads the critical prerequisite (sign-in required) before describing the action, and each sentence carries distinct information. Slightly dense but no filler; four sentences all earn their place.

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 mutating, open-world tool with no output schema, the description covers the workflow, side effects, and auth prerequisites well. However, the undefined `plan` and `service` parameters leave a real gap, and the return/result of enabling is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% – just `session` is documented in the schema, and the description merely restates its sign-in context without adding more. The `service` and `plan` parameters are undocumented in both schema and description; `plan` in particular is unexplained, so the description fails to compensate for the low coverage as it should.

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: 'Enable a federated service on your Datailo account,' and explains the downstream effect (datailo_tools and datailo_invoke reach it through this connection). It is clearly distinguishable from the opposite action datailo_disable, though it never names that sibling explicitly for contrast.

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?

Gives an explicit prerequisite chain: call datailo_connect(email) and datailo_connect_verify first unless already signed in, and notes the session requirement for subsequent calls. It doesn't state when to use an alternative (e.g., datailo_disable) or any exclusion cases, so it stops short of full routing guidance.

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

All Datailo: one MCP connection to tenders, EU regulation and law 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