Skip to main content
Glama

da_admin_create_source

Creates HTML or JSON source content files in an organization repository, using predefined templates for HTML or multi-sheet spreadsheet structures for JSON.

Instructions

Create source content within an organization: can be an html file or a json file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
extYesThe source content file extension: html or json
orgYesThe organization
pathYesPath to the source content
repoYesName of the repository
contentYes If extension is html: an html string using the following template: "<body><header></header><main><!-- content here --></main><footer></footer></body>". Only <main> should be populated with content. If extension is json: a json string representing a spreadsheet which can have multiple sheets. Each sheet can have an array of rows (represented as a data property). Each row can have as many cells as needed. A cell is a key / value pair. Simple sample: { "sheet1": { "total": 2, "data": [{ "column1": "value11", "column2": "value12", "column3": "value13" }, { "column1": "value21", "column2": "value22", "column3": "value23" }], }, ":names": [ "sheet1" ], ":type": "multi-sheet" }
Behavior2/5

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

No annotations provided. The description only says 'create' but does not disclose any behavioral traits such as side effects (e.g., overwrite, duplicate handling), authentication requirements, or rate limits. For a creation tool, this is insufficient.

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?

One sentence of 12 words, no fluff. Front-loaded with purpose. However, it could be slightly expanded for completeness without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, output schema, and 5 required parameters, the description is too sparse. It does not cover return values, error handling, or constraints like path format, leaving gaps for an agent.

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 description coverage is 100%. The description adds value by summarizing ext options and providing detailed templates for the content parameter, which goes beyond the schema's descriptions.

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 clearly states the tool creates source content (HTML or JSON files) within an organization, distinguishing it from sibling tools like list, get, delete.

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?

No explicit guidance on when to use this tool vs alternatives. The purpose is implied by the name and siblings, but no when-not or scenarios are provided. Adequate but missing explicit context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kptdobe/mcp-da-live-admin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server