Skip to main content
Glama

Declared interests of a council member

get_member_interests
Read-only

Retrieve a Swiss Federal Assembly member's declared interests, mandates, board seats, advisory roles, and occupations by last name or person number for lobbying transparency checks.

Instructions

Lobbying transparency: the declared interests and mandates of a member of the Federal Assembly (board seats, advisory roles, associations, foundations) with the organisation, the member's function, the type of interest and organisation, and paid/unpaid where published, plus declared occupations. Look up by last name (e.g. 'Noser', optionally first_name) or exact person_number (ID from search_council_members). Examples: {name:'Bregy'}; {name:'Müller', first_name:'Damian'}; {person_number:4057}.

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": "get_member_interests"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLast name (or fragment), e.g. 'Noser'
limitNo
languageNoDE
first_nameNoFirst name to disambiguate common surnames
person_numberNoExact PersonNumber (ID from search_council_members)
include_occupationsNoAlso return declared occupations/employers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantive context: the returned fields, the include_occupations toggle (default true), and the caveat that paid/unpaid data is only present 'where published'. It omits how the limit (default 60, max 100) and language parameters affect results, which is a meaningful remaining gap for a query tool.

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?

The definition is front-loaded with the resource and its payload, then the lookup keys, then inline examples; each sentence carries information. The enumeration of interest types in the first sentence is slightly long but earns its place by telling the agent what to expect back.

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?

With no output schema, the description usefully describes the returned structure and mentions the occupations payload controlled by include_occupations. For a read-only single-entity lookup it is nearly complete; only result-size/paging behaviour and the language parameter are unaddressed.

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?

Schema coverage is only 67%, and the description compensates by giving concrete usage examples for name, first_name and person_number, clarifying that name matches on last-name fragments and first_name is for disambiguation. It says nothing about limit or language, leaving two parameters documented only by type/default in the 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?

The description names a specific verb and resource ('the declared interests and mandates of a member of the Federal Assembly') and enumerates the concrete contents (board seats, advisory roles, associations, foundations). It distinguishes itself from the sibling search_council_members by naming it explicitly as the source of person_number.

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?

It states the two lookup paths (last name with optional first_name, or exact person_number) and points to search_council_members when an ID is needed. It doesn't say what to do when a name is ambiguous or when to prefer person_number over name beyond the 'exact' hint, so it falls short of full when/when-not guidance.

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