Skip to main content
Glama
Sign In
@afferens/mcp-server

@afferens/mcp-server

by afferens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

afferens_demo

Get real-time sensory data from six modalities — vision, spatial, acoustic, environmental, molecular, interoception. Free demo for AI agents.

Instructions

Get real-time physical perception data from all 6 Afferens sensory modalities — VISION, SPATIAL, ACOUSTIC, ENVIRONMENTAL, MOLECULAR, and INTEROCEPTION. No API key required. Use this to demonstrate what live sensor data looks like before your AI agent is fully wired up. Free to call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "afferens_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states real-time, free, no API key, and demo purpose. Does not explicitly declare read-only or non-destructive nature, but context implies safety. Adequate but not fully exhaustive.

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?

Three sentences, each adding distinct value: what the tool does, usage context, and cost. No fluff, well front-loaded.

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?

Given no parameters, no output schema, and no annotations, the description is nearly complete for a demo tool. It explains inputs (none), purpose, and usage. Could mention limits or that it's sample data, but not required.

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; baseline is 4. Description adds value by explaining what data will be returned (6 modalities, real-time), which is meaningful beyond schema.

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?

Description clearly states the verb 'Get', the resource 'real-time physical perception data', and enumerates all 6 sensory modalities. It distinguishes from siblings by positioning itself as a demo tool.

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 says 'Use this to demonstrate what live sensor data looks like before your AI agent is fully wired up' and notes no API key required. Clearly indicates demo usage context, though doesn't explicitly state alternatives.

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