Skip to main content
Glama
yyy188
by yyy188

configure_jama

Apply environment variable values for Jama, embedding, and database settings, persist them to .env, and reload configuration in process.

Instructions

Apply configuration values at runtime and persist them to .env.

Accepts a mapping of env-var names to values (e.g.
``{"JAMA_URL":"...","JAMA_CLIENT_SECRET":"..."}`). Writes a complete
``.env`` (merging with existing values), reloads settings in-process, and
resets the Jama/RAG/DB singletons so subsequent calls use the new config.
Secrets are written to ``.env`` on disk only; they are never echoed back.

Args:
    values: dict of {ENV_VAR: value}. Recognized keys: JAMA_URL,
            JAMA_CLIENT_ID, JAMA_CLIENT_SECRET, EMBEDDING_BASE_URL,
            EMBEDDING_API_KEY, JAMA_MCP_DB_PATH,
            and any other key in the .env template.

Returns:
    {"ok": true, "written": <abs .env path>, "applied_keys": [...]}
    or {"error": ...}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valuesYes
Behavior4/5

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

No annotations are provided, so the description fully handles transparency. It discloses that the tool writes to .env, merges with existing values, reloads settings, and resets singletons. It also notes secrets are never echoed back. This is fairly comprehensive, though it could mention side effects like overwriting existing values.

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?

The description is concise and well-structured with Args and Returns sections. Every sentence adds value, and there is no redundant information. It is efficient for the agent to parse.

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?

Given the tool's complexity (modifying persistent state, resetting singletons), the description covers essential aspects: input format, merge behavior, security (no secret echo), and return schema. However, it does not address error scenarios beyond returning an error dict, nor does it mention prerequisites or potential permission issues.

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?

The schema only defines a generic object with additionalProperties. The description adds significant meaning by listing recognized keys (JAMA_URL, etc.), stating it accepts a mapping, and noting that any key from the .env template is valid. This helps the agent understand parameter structure and valid keys.

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 applies configuration values at runtime and persists them to .env. It uses specific verbs ('apply', 'persist') and identifies the resource (configuration). Sibling tools like bootstrap_models or search functions are clearly distinct.

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?

The description explains when to use the tool (to apply configuration values) but does not explicitly state when not to use it or suggest alternatives. However, given the sibling set, it's evident that this is the only configuration tool.

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/yyy188/jama-mcp-server'

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