Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Connect a data source to a section

connect_data_source

Connect a PUBLIC endpoint or feed (one that needs no key) to one of the site's content sections, so the section's items come from it. The data is fetched when the site is published and built into the pages — it is not live in the browser — so the owner must republish (or sync the source in settings) for changes to show. Call list_bindable_content_keys and test_data_source_connection first. A section that already has a source must be disconnected in settings first. Endpoints that need a key are connected in the site's Data Sources settings.

Input Schema

NameRequiredDescriptionDefault
nameYesA label, e.g. "Live pricing"
site_idYesThe site, from list_sites
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
content_keyYesThe section it fills — exactly one of the paths from list_bindable_content_keys
source_typeYes"rest_api" for any JSON/HTTP endpoint, "rss" for an RSS/Atom feed
endpoint_urlYesThe full public address to fetch
field_mappingNo{ "<source field>": "<section field>" }; source keys may be dot-paths, targets are flat field names
response_pathNoDot-path to the list inside the JSON
refresh_interval_minutesNoRe-fetch on a schedule, in minutes. Omit for manual refresh only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the generic profile (openWorldHint=true, idempotentHint=false, destructiveHint=false). The description adds the non-obvious operational semantics: data is fetched at publish time and baked into pages, not live in the browser, so a republish or settings sync is required for changes to appear. It also discloses that an existing source blocks the connection, which is real behavioral context the annotations cannot convey.

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?

Five short sentences, all load-bearing, with the scope constraint front-loaded before the prerequisites and the alternative route. Nothing is repeated from the title or the schema.

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 9-parameter mutation with nested objects and no output schema, the description covers scope, prerequisites, ordering constraints and publish-time behavior well. The remaining gap is what the call returns (e.g. the created data source identifier or a mapping result), which the agent cannot learn from an output schema that does not exist.

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 100%, so the baseline is 3. The description still adds constraint semantics the schema does not state: endpoint_url must be public and key-free, and content_key must be exactly one path returned by list_bindable_content_keys. field_mapping, response_path and refresh_interval_minutes are left entirely to the schema.

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?

States a specific verb and resource (connect a public endpoint/feed to a content section) and the effect (the section's items come from it). It explicitly scopes out key-based endpoints and points those to the site's Data Sources settings, which separates it from sibling data-source tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives ordered prerequisites (call list_bindable_content_keys and test_data_source_connection first), an exclusion (endpoints needing a key are connected in settings, not here), and a blocking condition (a section that already has a source must be disconnected first). An agent knows when and when not to call it.

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

All Mondovo 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