Skip to main content
Glama

Symvanta

by com.symvanta
OverviewDiscussionsAdmin

ref

Idempotent

Session-scoped branch / working-tree overlay / project binding. Ops:

  • use: pin a repository's reads to a branch (latest indexed revision). Branch must be tracked+indexed (open a PR, or add on the dashboard); else "indexing_in_progress". commitSha overrides.

  • clear: remove the pin, revert to default.

  • index_working_tree: overlay UNCOMMITTED edits (changedFiles path+content, optional deletedPaths/baseSha) on a short-lived synthetic revision pinned here; find_node/locate/relate reflect them, source and locate mode:semantic do NOT. Cap 100 files/256KB.

  • use_project: bind this session to projectId (from init.otherProjects / list_projects / create_project) so calls without projectId resolve there. init with repository:"owner/name" sets the same binding from the checkout's remote.

  • clear_project: drop the binding, back to the workspace default project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYesuse: pin reads to a tracked branch. clear: revert to the default branch. index_working_tree: overlay uncommitted edits on a synthetic revision and pin it. use_project: bind this session to projectId so calls without projectId resolve there. clear_project: revert to the workspace default project.
branchNoop:use. The tracked branch to pin.
baseShaNoIndexed base your edits sit on. Omit for the default-branch tip.
feedbackNoOptional: report how a previous answer worked out; piggybacks on any call.
projectIdNoProject id from init/list_projects. Omit for the active project.
repositoryNoRepository full name, e.g. "owner/repo". Omit when the project has one repository.
changedFilesNoChanged/added files with current contents, repo-relative paths.
deletedPathsNoRepo-relative deleted paths.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / op / description
      Previous value: -"use: pin reads to a tracked branch. clear: revert to the default branch. index_working_tree: overlay uncommitted edits on a synthetic revision and pin it."New value: +"use: pin reads to a tracked branch. clear: revert to the default branch. index_working_tree: overlay uncommitted edits on a synthetic revision and pin it. use_project: bind this session to projectId so calls without projectId resolve there. clear_project: revert to the workspace default project."
    • changedInput schema / properties / op / enum
      Previous value: -[
-  "use",
-  "clear",
-  "index_working_tree"
-]New value: +[
+  "use",
+  "clear",
+  "index_working_tree",
+  "use_project",
+  "clear_project"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover safety (non-readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: a short-lived synthetic revision, the 100-file/256KB cap, the 'indexing_in_progress' failure mode, and the crucial limitation that find_node/locate/relate see the overlay while source and locate mode:semantic do not.

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?

Front-loaded with a one-line identity followed by a clean bullet per op, so each sentence maps to a mode. It is dense with internal jargon (find_node/locate/relate, mode:semantic) and the stale commitSha reference slightly weakens it, but nothing is padding.

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 8 parameters, nested objects, and no output schema, the burden falls on prose, and the description covers op semantics, side effects, prerequisites, and error codes well. It stops short of describing return values or what a successful pin/binding yields, and it omits the piggybacked feedback flow.

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 coverage is 100%, so the baseline is 3, but the description adds real semantic constraints (tracked+indexed prerequisite, cap limits, baseSha omission behavior). It is docked slightly because it references a 'commitSha' override that does not exist in the schema (baseSha is the actual field) and never mentions the feedback parameter.

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?

Names the resource ('session-scoped branch / working-tree overlay / project binding') and then enumerates each of the five ops with a specific verb and effect. An agent can tell it apart from index_health, reindex_repository, and init without opening the schema.

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

Usage Guidelines5/5

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

States activation conditions per op: branch must be tracked+indexed otherwise 'indexing_in_progress', commitSha (as described) overrides, projectId comes from init.otherProjects/list_projects/create_project, and binding via repository:"owner/name" on init. It also tells the agent which downstream tools the overlay does and does not affect.

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

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