Skip to main content
Glama

vybsly_directions

Get turn-by-turn driving directions between two locations. Specify start and end points to receive step-by-step route guidance.

Instructions

Get turn-by-turn driving directions between two places.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYes
toYes

Implementation Reference

  • index.js:160-171 (registration)
    Tool registration with name 'vybsly_directions', description, and inputSchema defining 'from' and 'to' string parameters.
    {
      name: 'vybsly_directions',
      description: 'Get turn-by-turn driving directions between two places.',
      inputSchema: {
        type: 'object',
        properties: {
          from: { type: 'string' },
          to: { type: 'string' }
        },
        required: ['from', 'to']
      }
    }
  • Input schema for vybsly_directions: requires 'from' and 'to' as string properties.
    inputSchema: {
      type: 'object',
      properties: {
        from: { type: 'string' },
        to: { type: 'string' }
      },
      required: ['from', 'to']
    }
  • Handler for vybsly_directions tool: calls vybslyCall('/directions', { from: args.from, to: args.to }) and returns the result as JSON text.
    case 'vybsly_directions':
      result = await vybslyCall('/directions', { from: args.from, to: args.to });
      break;
  • Helper function vybslyCall() that makes HTTP GET requests to the Vybsly API with query parameters and API key header.
    async function vybslyCall(path, params = {}) {
      const qs = new URLSearchParams(params).toString();
      const url = `${VYBSLY_BASE}${path}${qs ? '?' + qs : ''}`;
      const headers = { 'Accept': 'application/json' };
      if (API_KEY) headers['X-API-Key'] = API_KEY;
      const res = await fetch(url, { headers });
      if (!res.ok) {
        const text = await res.text();
        throw new Error(`Vybsly API ${res.status}: ${text.slice(0, 300)}`);
      }
      return res.json();
    }
Behavior2/5

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

No annotations provided; description fails to disclose output format, traffic consideration, or whether it supports multiple routes. For a read operation, more detail is needed.

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 sentence that is efficient and to the point, with no unnecessary words.

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

Completeness2/5

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

With no output schema, no annotations, and minimal parameter info, the description is insufficient for an agent to fully understand what the tool returns or how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage; description adds no format guidance for 'from' and 'to' (e.g., address, city, coordinates), leaving semantics ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides turn-by-turn driving directions between two places, distinguishing it from siblings like geocode (coordinates) or search (general queries).

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

Usage Guidelines2/5

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

No guidance on when to use versus alternatives (e.g., geocode for coordinates) or prerequisites (e.g., valid place names). The agent must infer context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BlueFusionLab/vybsly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server