Skip to main content
Glama

Symvanta

by com.symvanta
OverviewDiscussionsAdmin

init

Read-onlyIdempotent

Call first, with repository:"owner/name" (your checkout's GitHub remote). Binds the session to the project holding that repository and returns it as the active project with its repositories, index health, and a usage field (decision matrix + routing). workspace.attached=false means the checkout is NOT indexed: nothing in the answer describes it; attach it (add_repository, create_project) or work without the graph, do not route through the projects listed. Without repository: the pinned project (ref op:"use_project") or the workspace default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedbackNoOptional: report how a previous answer worked out; piggybacks on any call.
repositoryNoThe checkout's GitHub remote as "owner/name" (a clone URL is accepted). Binds the session to the project holding it; workspace.attached=false means it is not indexed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / repository
      Added value: +{
+  "description": "The checkout's GitHub remote as \"owner/name\" (a clone URL is accepted). Binds the session to the project holding it; workspace.attached=false means it is not indexed.",
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real behavioral context: the return payload (active project, repositories, index health, `usage` field) and the meaning of workspace.attached=false. It notes the session-binding side effect but does not resolve the mild tension between 'Binds the session' and readOnlyHint=true, which would be worth one clarifying clause.

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-loads the critical instruction ('Call first') and every sentence carries information, but the middle sentence is a dense run-on packed with parenthetical references (`usage` field, ref op:'use_project') that makes parsing harder than necessary.

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

Completeness5/5

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

No output schema exists, so the description must carry return-value meaning, and it does (active project, repositories, index health, usage/decision matrix). Both the repository and no-repository branches are covered, leaving nothing essential for a correct call unstated.

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 the fallback resolution when repository is omitted (pinned project via ref op:'use_project' or workspace default), which the schema does not encode. This goes beyond the schema's 'owner/name / clone URL accepted' text.

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 concrete verb+resource: it 'Binds the session to the project holding that repository' and returns it as the active project. It also names the siblings it is not (add_repository, create_project) and the other project-selection path (ref op:'use_project'), so an agent can distinguish it 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 Guidelines5/5

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

Explicit ordering ('Call first'), explicit scenario branches (with repository vs without repository), and explicit alternatives for the not-indexed case (attach via add_repository/create_project, or 'work without the graph'). It even states a prohibition: 'do not route through the projects listed.'

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