Skip to main content
Glama

vybsly_weather

Retrieve current weather and 5-day forecast for any city by providing its name.

Instructions

Current weather and 5-day forecast for a city.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity name, e.g. Miami or "New York"

Implementation Reference

  • Tool schema definition for vybsly_weather — declares the tool name, description, and input schema requiring a 'city' parameter.
    {
      name: 'vybsly_weather',
      description: 'Current weather and 5-day forecast for a city.',
      inputSchema: {
        type: 'object',
        properties: {
          city: { type: 'string', description: 'City name, e.g. Miami or "New York"' }
        },
        required: ['city']
      }
    },
  • Handler logic for vybsly_weather — calls the Vybsly API /weather endpoint with args.city as the city parameter.
    case 'vybsly_weather':
      result = await vybslyCall('/weather', { city: args.city });
      break;
  • Helper function vybslyCall — generic HTTP fetch wrapper used by the weather handler to call the Vybsly API with query params.
    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();
    }
  • index.js:412-417 (registration)
    MCP server registration — creates the server and registers ListToolsRequestSchema handler which returns the TOOLS array containing vybsly_weather.
    const server = new Server(
      { name: 'vybsly-mcp', version: '1.1.0' },
      { capabilities: { tools: {}, prompts: {}, resources: {} } }
    );
    
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as data freshness, error handling, or rate limits. With the full burden on the description, this is insufficient.

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?

Single sentence, front-loaded with key information, no wasted words.

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

Completeness3/5

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

For a simple 1-parameter tool with no output schema, the description covers the basic purpose but lacks details on response format, units, or error cases.

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 input schema already describes the city parameter with examples; the description adds no further meaning beyond the schema, so baseline 3 applies.

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 it provides current weather and 5-day forecast for a city, which distinguishes it from sibling tools like stocks or news.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives, but the purpose implies it is for weather queries.

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