Skip to main content
Glama
LMPrado-DZ23

Universal AI Bridge

by LMPrado-DZ23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Informações do workspace

get_workspace_info

Retrieve workspace configuration before executing commands: get workspace name, mode, approval requirements, and shell/Docker availability. Optionally include the absolute path.

Instructions

Retorna nome do workspace, modo (safe/admin), aprovação e se shell/docker estão habilitados. Chame primeiro. Não revela o caminho absoluto por padrão (use include_absolute_path=true se precisar).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_absolute_pathNoIncluir o caminho absoluto do workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / include_absolute_path
      Added value: +{
+  "default": false,
+  "description": "Incluir o caminho absoluto do workspace",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Despite no annotations providing safety hints, the description discloses a key behavioral trait: it does not reveal the absolute path by default, which is a significant behavior for an agent to know. It also implies it is a safe read operation (returns info), though it doesn't explicitly state no side effects. The single default-behavior caveat adds value beyond the schema, which only shows the parameter default. Given the simplicity of the tool, this is strong disclosure, but it could have gone further to explicitly state that it makes no modifications or requires no special auth.

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?

Two sentences with zero filler. The key 'Chame primeiro' instruction is front-loaded, and the parameter caveat is placed at the end, making it scannable. Every phrase earns its place: the list of returned fields, the usage order, and the default behavior caveat.

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 single-parameter, read-only info tool without an output schema, the description is highly complete. It tells the agent what fields are returned, that it should be called first, and the only caveat about the absolute path. Minor gaps: no mention of error conditions (e.g., what if called outside a workspace) or whether the returned fields are always present, but these are not critical for a first-step introspection tool.

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?

The schema already covers 100% of the single parameter's description, so the baseline is 3. The description adds context by explaining why the parameter might be needed ('se precisar'), but it does not add new meaning beyond the schema's own description. It effectively reinforces the schema, which is acceptable but not additional value.

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 returns workspace metadata (name, mode, approval, shell/docker status), and the verb 'Retorna' is specific. It is distinct from siblings like read_file or get_file_info because it focuses on workspace-level info, and it even includes the key exclusion of the absolute path by default, which differentiates it from file-path-related tools.

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?

Explicitly instructs 'Chame primeiro' (call first), establishing a clear usage order. It also states when to use an optional parameter ('use include_absolute_path=true se precisar'), though it does not explicitly mention when not to use this tool or alternatives. However, for a single-purpose info tool, this guidance is sufficient and actionable.

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

Deploy Server

Other Tools