Skip to main content
Glama
tudadada

mcp-server-valuation

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
value_digital_assetC

Calculates valuation models for digital assets, premium domains, and web properties based on liquid floors and enterprise multiples.

calc_ebitda_multipleC

Calculates target acquisition value based on annual revenue/EBITDA and industry-standard multiples.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 2 tools

Disambiguation4/5

The two tools target somewhat different resources: value_digital_asset focuses on domains/web properties, while calc_ebitda_multiple computes acquisition value from EBITDA. However, both involve valuation multiples, which could cause occasional confusion.

Naming Consistency4/5

Both names follow a snake_case verb_noun pattern, but one uses the full verb 'value' while the other abbreviates 'calc', a minor deviation.

Tool Count3/5

Only two tools for a valuation server feels thin; the domain likely supports several more methods, making the count borderline but not unreasonable for a highly focused server.

Completeness2/5

The surface covers only digital asset valuation and EBITDA multiple calculation, missing common approaches like DCF, comparable companies, and revenue multiples. These gaps would cause failures for many general valuation requests.

Maintenance

ActivityMaintained
ResponsivenessNo issues