Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

skills_create

Save a new skill of your own: a routine the agent can run for you on your connected accounts. Private to you. Takes the title, the situation it is for, what it produces, the skill file (markdown, the same shape as a published skill), the tools it uses, and whether it runs on a single account or multiple. Answers with the slug and version.

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": {
      "title": "<title>",
      "source": "<source>",
      "tools": "<tools>"
    },
    "name": "skills_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesQuery-shaped, like a published skill's title.
toolsYesThe tools it uses, by name.
sourceYesThe skill file itself, markdown with frontmatter.
accountsNoOptional; single by default.
producesNoWhat the run produces. Optional.
situationNoThe problem, in your words. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden and does add value: visibility ("Private to you"), the return shape ("Answers with the slug and version"), and a format constraint (the skill file must match a published skill's shape). It stops short of covering duplicate-title handling, validation failures, or whether re-creation overwrites anything.

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?

Purpose and privacy are front-loaded, and the sentence about the return value is high-value. The middle sentence is a long comma-separated inventory that partly duplicates the schema, which is the only real waste.

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?

With six parameters, three required, and no output schema, the description supplies what structured fields do not: what a skill is, that it is private, and that creation returns a slug and version. The remaining gap is sibling disambiguation against update/fork.

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 100%, so the baseline is 3; the description mostly re-enumerates the fields the schema already documents. The one genuine addition is the reference model for source ("the same shape as a published skill"), though the flat list risks implying situation and produces are required when the schema marks them optional.

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 opens with a specific verb+resource ("Save a new skill of your own") and defines what a skill is ("a routine the agent can run for you on your connected accounts"). The words "new" and "Private to you" separate it from skills_update, skills_fork, and the published-skill catalog, so an agent can route correctly without opening a schema.

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

Usage Guidelines3/5

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

It implies when to use it (creating a brand-new private routine) and clarifies the account-scope choice via the accounts parameter, but it never names alternatives such as skills_update for edits or skills_fork for copying an existing skill. Usage is inferable rather than stated.

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

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