Skip to main content
Glama

Saved versions of a function

dosai_list_function_versions
Read-onlyIdempotent

Earlier states of one function, newest first (up to 50): version_id, when it was saved and what the function was called and did then. Roll back with dosai_restore_function_version. Requires editor role.

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": {
      "project_id": "<project_id>",
      "function_id": "<function_id>"
    },
    "name": "dosai_list_function_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
function_idYesFrom dosai_list_functions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / function_id / description
      Previous value: -"Function id, as returned by dosai_list_functions."New value: +"From dosai_list_functions."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  3. Changed2 schema fields changed
    • removedInput schema / properties / function_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the read-only, idempotent, non-destructive profile, so the description doesn't need to restate safety. It earns credit for disclosing traits annotations can't express: the maximum of 50 results, newest-first ordering, and the editor-role permission requirement. It doesn't say whether the cap is a hard window or paginated, which keeps it off a 5.

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?

A single dense sentence front-loads the resource and ordering, then the return fields, then the sibling and the permission gate — no wasted words. The phrase "what the function was called and did then" is slightly tangled and costs a point on readability.

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 no output schema, the description correctly takes on the job of naming the returned fields, and it covers ordering, cap, and access prerequisites for a simple two-parameter read. The only gap is truncation behavior — an agent can't tell whether 50 is a total cap or a page size.

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 description coverage is 100% and both parameters are self-documenting with cross-references to dosai_list_projects and dosai_list_functions, so the baseline of 3 applies. The description adds only the implicit scoping to one function, which the names project_id/function_id already convey.

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 states a specific resource (earlier states of one function) and adds distinguishing detail no sibling could share: newest-first ordering, a 50-item cap, and the returned fields (version_id, save time, then-current name and behavior). An agent can tell this apart from dosai_list_functions and dosai_list_prompt_versions 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 Guidelines4/5

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

It names the follow-up action tool explicitly ("Roll back with dosai_restore_function_version"), which implies the inspection-then-restore workflow, and states the access prerequisite ("Requires editor role"). What's missing is an explicit when-not or a statement of what happens when there are zero versions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources