Skip to main content
Glama
Sign In

Tevyon

by ai.tevyon
OverviewDiscussionsAdmin

Share in the community

set_visibility
Idempotent

Makes one of the account's finished results public in the Tevyon community, or private again (the default). Only on the user's request. Needs a community profile, which a person sets up in Tevyon Studio. show_prompt: whether others see the prompt (default: the profile's choice). consent: needed once for a result made from an own upload (photo, video); pass true only if the account holds the rights and every recognisable person agreed to it being public.

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": {
      "job_id": "<job_id>",
      "visibility": "<visibility>"
    },
    "name": "set_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesA succeeded job of this account (generate, list_jobs).
consentNo
visibilityYes
show_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the result must be finished and belong to the account, the community profile prerequisite, the default of private, and the legal/rights condition on consent. This is consistent with the annotations (idempotent toggle, non-destructive, closed-world).

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?

Dense but front-loaded: the core action and default come first, then prerequisites, then per-parameter semantics. The consent sentence is long and packs two conditions, but no sentence is wasted.

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 4-parameter mutation with no output schema, the description covers prerequisites, defaults, consent conditions, and the direction of the state change. It omits what happens when the profile is missing (error behavior), which is a minor remaining gap.

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 only 25%, so the description must carry the load; it explains show_prompt's meaning and default inheritance from the profile, and defines consent's condition precisely. Only `visibility` is left to its self-explanatory enum, so coverage is nearly complete.

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 ('Makes one of the account's finished results public ... or private again') plus the default direction. It immediately tells the agent this is a community-visibility toggle scoped to a finished result, which no sibling tool does.

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?

Gives clear usage conditions: 'Only on the user's request' and a prerequisite that a community profile must exist in Tevyon Studio. It does not name the sibling `request_consent` as the route for obtaining consent, so the routing to alternatives is implied rather than explicit.

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

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