Skip to main content
Glama
Sign In

Edgegap

by dev.edgegap
OverviewDiscussionsAdmin
This connector has been deprecated

older mcp we are replacing it with another one.

Create a pull profile (copy bucket files into containers)

edgegap_create_pull_profile

Create a pull profile under an Endpoint Storage: at boot, Edgegap copies a file or folder from the bucket into the container (maps, configs, large assets kept out of the image). It does nothing until linked to a version with edgegap_link_pull_profile. Avoid destination paths the image already uses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint_storage": "<endpoint_storage>",
      "name": "<name>",
      "source": "<source>",
      "source_type": "<source_type>",
      "destination": "<destination>"
    },
    "name": "edgegap_create_pull_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the profile, e.g. "maps".
sourceYesPath in the bucket, starting with "/" and without a trailing "/", e.g. "/maps" or "/config/server.json". Letters, digits, "_", "-", "+" and "." only.
dry_runNoShow the exact request (method, host, path, body) with secrets masked, and send nothing. Local checks still run. Use it to confirm a billable or destructive call before making it.
destinationYesAbsolute path in the container, e.g. "/data/maps".
source_typeYesWhether source is a file or a folder.
endpoint_storageYesEndpoint Storage name, from edgegap_list_endpoint_storage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds meaningful behavioral context beyond that: the copy happens at container boot, the profile does nothing until linked, and destination paths used by the image should be avoided. It does not discuss permissions or return behavior, but the core lifecycle behavior is disclosed well.

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?

Three tightly written sentences front-load the action, then explain the boot-time copy and the linking dependency. The parenthetical examples and destination warning are useful and do not bloat the definition.

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 create tool with five required parameters and 100% schema description coverage, the description is nearly complete: it explains purpose, lifecycle, next step, and a destination-path caveat. The main minor gap is that it does not describe what the create call returns or whether the profile can be reused across versions.

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 parameter descriptions already carry most semantic weight. The description still adds useful meaning for destination by warning against paths the image already uses, and it clarifies that source refers to a bucket file or folder copied into the container; dry_run and endpoint_storage details are left 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?

The description states a specific verb and resource: "Create a pull profile under an Endpoint Storage." It immediately explains the effect at boot (copying a file or folder from the bucket into the container) and names the related sibling edgegap_link_pull_profile, so the tool is clearly distinguishable from create_endpoint_storage and link_pull_profile.

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?

It gives clear usage context: the profile is inert until linked with edgegap_link_pull_profile, and destination paths already used by the image should be avoided. That covers prerequisites and a key caveat, though it does not explicitly frame when to choose this versus another profile/storage approach beyond the linking dependency.

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

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