Skip to main content
Glama
Prototypr

Feedbagel MCP Server

Official
by Prototypr

me

Check API authentication by retrieving the authenticated account's email, plan, and status.

Instructions

[read] Return the authenticated account's email, plan, and status. Use as a smoke test before other calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'me' tool. It takes no input (z.object({})), makes a GET request to '/api/v1/me' using the FeedbagelClient, and returns the authenticated account's email, plan, and status.
    handler: (_, c) => c.request("GET", "/api/v1/me"),
  • Input schema for the 'me' tool: an empty object (z.object({})), meaning no parameters are required or accepted.
    inputSchema: z.object({}),
  • src/tools.ts:118-125 (registration)
    The 'me' tool is defined as an entry in the TOOLS array (ToolDef[]), with name 'me', description, scope 'read', empty input schema, and the handler function. It is registered in the MCP server via the ListToolsRequestSchema and CallToolRequestSchema handlers in src/index.ts.
    {
      name: "me",
      description:
        "Return the authenticated account's email, plan, and status. Use as a smoke test before other calls.",
      scope: "read",
      inputSchema: z.object({}),
      handler: (_, c) => c.request("GET", "/api/v1/me"),
    },
  • The FeedbagelClient.request() method is the helper that actually executes the HTTP request. The 'me' handler calls c.request('GET', '/api/v1/me'), which sends an authenticated GET request to the feedbagel API.
    async request(
      method: string,
      path: string,
      body?: unknown,
    ): Promise<unknown> {
      const res = await fetch(`${this.baseUrl}${path}`, {
        method,
        headers: {
          Authorization: `Bearer ${this.apiKey}`,
          ...(body !== undefined ? { "content-type": "application/json" } : {}),
        },
        body: body !== undefined ? JSON.stringify(body) : undefined,
      });
    
      const text = await res.text();
      let json: unknown = undefined;
      try {
        json = text ? JSON.parse(text) : undefined;
      } catch {
        json = { raw: text };
      }
    
      if (!res.ok) {
        // Surface 429 and 4xx details verbatim so the agent sees the cap info.
        const err: Error & { status?: number; body?: unknown } = new Error(
          `HTTP ${res.status} ${res.statusText}`,
        );
        err.status = res.status;
        err.body = json;
        throw err;
      }
      return json;
    }
Behavior4/5

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

The '[read]' prefix indicates a read-only operation, and it lists specific return fields. No annotations exist, so the description carries the burden. It lacks details on authentication requirements or rate limits, but for a simple read tool, the transparency is adequate.

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, front-loaded with purpose and immediately followed by usage hint. Every word adds value, no fluff.

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?

For a zero-parameter, no-output-schema tool, the description fully conveys what it does and when to use it. It is complete for its simplicity.

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?

No parameters exist, and schema coverage is 100%. The description does not need to add parameter info; a baseline of 4 is appropriate as it fulfills the minimum without needing compensation.

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 the authenticated account's email, plan, and status. It distinguishes from sibling tools (which handle feeds, webhooks, entries) by focusing on account info.

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

Usage Guidelines4/5

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

Explicitly suggests using as a smoke test before other calls, providing clear context. Does not mention when not to use, but the hint is strong enough for appropriate usage.

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/Prototypr/feedbagel-mcp'

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