Skip to main content
Glama
polytechub-code

Kraviona Admin MCP Server

update_site_settings

Update global site settings including address, logo, site name, contact info, social links, and SEO metadata to manage site configuration.

Instructions

Update global site settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNo
logoUrlNo
siteUrlNo
siteNameNo
faviconUrlNo
facebookUrlNo
linkedinUrlNo
siteTaglineNo
contactEmailNo
contactPhoneNo
twitterHandleNo
defaultMetaDescNo
siteDescriptionNo
defaultMetaTitleNo
googleAnalyticsIdNo
Behavior1/5

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

No annotations exist, and the description does not disclose any behavioral traits such as mutability, destructiveness, permissions, or side effects. It merely repeats the action implied by the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is concise (one sentence), it is under-specified. It does not earn its place by providing useful information beyond the tool name.

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

Completeness1/5

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

Given 15 parameters, no output schema, and no annotations, the single-sentence description is grossly inadequate. It fails to cover essential aspects of tool usage.

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

Parameters1/5

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

The description does not mention any of the 15 parameters. With 0% schema description coverage, the description provides zero insight into parameter meaning or usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update global site settings' clearly states the verb and resource, but it is vague about what specific settings are updated. Since there are no sibling tools, differentiation is not needed, but the description could be more precise.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool or any prerequisites. The description lacks context for appropriate usage scenarios.

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/polytechub-code/mcp-kraviona.com'

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