Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VTENEXT_URLYesURL of your VTENext instance (e.g., http://your-vtenext-instance)
VTENEXT_USERNAMEYesVTENext username (e.g., admin)
VTENEXT_ACCESS_KEYYesVTENext access key found under Admin → Users → [user] → Access Key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_opportunitaC

Elenca le opportunità con filtri opzionali

get_opportunitaC

Recupera i dettagli completi di un'opportunità tramite ID

search_opportunitaC

Cerca opportunità per nome

create_opportunitaC

Crea una nuova opportunità in VTENext

update_opportunitaC

Aggiorna i dati di un'opportunità esistente

search_contattiC

Cerca contatti per nome, email o azienda

add_nota_opportunitaC

Aggiunge una nota/commento a un'opportunità

list_attivita_opportunitaC

Elenca le attività associate a un'opportunità

describe_moduloC

Mostra i campi disponibili per un modulo VTENext

query_rawC

Esegue una query VTQL grezza su VTENext (solo lettura)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. For example, list_opportunita retrieves multiple records with filters, get_opportunita fetches a single record by ID, and search_opportunita finds records by name. The tools target different resources (opportunità, contatti, modulo) and actions (create, update, list, search, describe, query).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case. Verbs like add, create, describe, get, list, query, search, and update are used predictably with corresponding nouns (e.g., add_nota_opportunita, create_opportunita, describe_modulo). There are no deviations in naming conventions.

Tool Count5/5

With 10 tools, the count is well-scoped for managing opportunities and related data in VTENext. Each tool serves a clear purpose, such as CRUD operations for opportunities, searching contacts, listing activities, and raw queries. No tool feels redundant or unnecessary for the server's domain.

Completeness5/5

The tool set provides complete coverage for the VTENext opportunity management domain. It includes full CRUD (create, get, update, list/search) for opportunities, plus related operations like adding notes, listing activities, searching contacts, describing modules, and raw queries. There are no obvious gaps, and agents can handle typical workflows without dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues